Magnus Hagander wrote:
I get a popup box that says:
initdb.exe has encountered a problem and needs to close.
We are sorry for the inconvenience.
Clicking a link gives this info:
AppName: initdb.exe AppVer: 8.2.0.6051 ModName: msvcrt.dll
ModVer: 7.0.2600.1106 Offset: 00033830
It wouldn't let me copy the rest of the info ;-(
Hm. Crap. (For those not familiar with this, that's a coredump without a
core:-P)
Does it give you an error code? (Nevermind the stackdump etc, just the
code)
I'll have a look when I get time to reboot the machine into Windows.
Are you running this with an admin account or a non-admin account? If
admin, what are the permissions on the initdb.exe file and libpq.dll?
Should be unprivileged - it's the account I use to run buildfarm. (and
which has therefore in each case just successfully run "make check" with
the identical binaries).
Anything weird in how you run it - do you specify a path to initdb, or
run it from current directory for example?
relative path: bin/initdb foo
(bin has libpq.dll as well as initdb.exe).
And finally, can you check with process explorer if it's the first or
second initdb that dies? (With this patch, initdb will re-exec itself
with lower privs)
I will add some trace writes when I get a chance. I was rather hoping
something would jump out at you, but obviously it hasn't, so I'll have
to dig into it the slow way. *sigh*
cheers
andrew
---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings
