Magnus Hagander wrote:
> Andrew Dunstan wrote:
>
>
>> I've installed drmingw to handle exceptions instead, so we'll see if
>> that gives us useful info. If not, I'll see what I can do with gdb.
>>
>
> Hadn't heard of drwmingw, I see how that can be useful :-)
>
>
>
report from DrMingw is below
cheers
andrew
initdb.exe caused an Access Violation at location 7c91b1fa in module
ntdll.dll Writing to location 20202030.
Registers:
eax=20202020 ebx=00000000 ecx=00000000 edx=003eab70 esi=003eab70
edi=00000000
eip=7c91b1fa esp=0022b820 ebp=0022b894 iopl=0 nv up ei pl nz na
po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000
efl=00000206
Call stack:
7C91B1FA ntdll.dll:7C91B1FA RtlpWaitForCriticalSection
7C901046 ntdll.dll:7C901046 RtlEnterCriticalSection
77C3F34F msvcrt.dll:77C3F34F _popen
00401493 initdb.exe:00401493 popen_check initdb.c:477
static FILE * popen_check( const char * command = , const char * mode =
) ... errno = 0; cmdfd = popen(command, mode);> if (cmdfd == NULL) fprintf(stderr, _("%s: could not execute
command\"%s\": %s\n"), progname, command, strerror(errno)); ...
00404DA0 initdb.exe:00404DA0 main initdb.c:1650
int main( int argc = 7, char * * argv = &0x003e3d21
) ... DEVNULL); > PG_CMD_OPEN; for (line = sysviews_setup; *line != NULL; line++) ...
004011E7 initdb.exe:004011E7
00401238 initdb.exe:00401238
7C817067 kernel32.dll:7C817067 RegisterWaitForInputIdle