Re: CVS HEAD busted on Windows?

> -----Original Message-----
> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
> Sent: 21 June 2006 14:30
> To: Dave Page
> Cc: Peter Eisentraut; pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] CVS HEAD busted on Windows?
>
> "Dave Page" <dpage@vale-housing.co.uk> writes:
> > killed it this morning (after 6+ hours of runtime) and it reported:
> > pg_regress: could not set database default locales
>
> That would be here:
>
> "$bindir/psql" -q -X $psql_options -c "\
> alter database \"$dbname\" set lc_messages to 'C';
> alter database \"$dbname\" set lc_monetary to 'C';
> alter database \"$dbname\" set lc_numeric to 'C';
> alter database \"$dbname\" set lc_time to 'C';" "$dbname"
> if [ $? -ne 0 ]; then
>     echo "$me: could not set database default locales"
>     (exit 2); exit
> fi
>
> Could you gdb the attached backend and see what it's doing?  Is it
> actually consuming CPU, or just stuck?

Hmmm, running it more interactively I see what was probably the hang
when run from the scheduler:

---------------------------
psql.exe - Application Error
---------------------------
The instruction at "0x7c8396d0" referenced memory at "0x00000014". The
memory could not be "read".
Click on OK to terminate the program
Click on CANCEL to debug the program
---------------------------
OK   Cancel
---------------------------

(if that got fired off under the scheduler it would appear to hang as
there would be no display to display it on, and no way to hit OK or
Cancel).

Unfortunately gdb is giving a somewhat useless backtrace (yes, this is a
debug build):

(gdb) bt
#0  0x7c822584 in ntdll!DbgUiIssueRemoteBreakin ()  from C:\WINDOWS\system32\ntdll.dll
#1  0x7c845ea0 in ntdll!EtwGetTraceEnableFlags ()  from C:\WINDOWS\system32\ntdll.dll
#2  0x00000005 in ?? ()
#3  0x00000004 in ?? ()
#4  0x00000001 in ?? ()
#5  0x00bfffd0 in ?? ()
#6  0x00000003 in ?? ()
#7  0xffffffff in ?? ()
#8  0x7c82f680 in ntdll!RtlGetNativeSystemInformation ()  from C:\WINDOWS\system32\ntdll.dll
#9  0x7c845eb0 in ntdll!EtwGetTraceEnableFlags ()  from C:\WINDOWS\system32\ntdll.dll
#10 0x00000000 in ?? () from
#11 0x00000000 in ?? () from
#12 0x00000000 in ?? () from
#13 0x00000000 in ?? () from
#14 0x00c00040 in ?? ()
#15 0x00000000 in ?? () from
#16 0x00000000 in ?? () from
#17 0x00000000 in ?? () from
#18 0x00000000 in ?? () from
<snip another 1000 or so lines>

Visual Studio can't do much better, but that's to be expected because it
can't understand the mingw debug symbols.

:-(

Regards, Dave.