Andrew Dunstan wrote: > > > Andrew Dunstan wrote: >> >> Something happened about 80 hours ago that caused my mingw buildfarm >> member (gcc 3.4.2 on Win XP Pro SP2) to hang at the check stage. It >> looks like it's hung in initdb. >> >> I wonder if it could be this commit: >> >> Log Message: >> ----------- >> Make win32 builds always do SetEnvironmentVariable() when doing putenv(). >> Also, if linked against other versions than the default MSVCRT library >> (for example the MSVC build which links against MSVCRT80), also update >> the cache in the default MSVCRT at the same time. >> >> I note that the change is not apparently limited to MSVC builds. The >> MSVC animal that runs on the same machine appears unaffected. I see >> one other mingw buildfarm member that is having problems that started >> a few days ago (yak) and another that looks like it is a few hours >> overdue to report, so it might also be hung (vaquita). >> >> > > Further to this: > > I see that vaquita has now reported in, and is happy. Also, I can run > happily on my Vista box (vaquita is also a Vista box). I therefore > suspect that we have a problem specifically with XP (both dawn_bat and > yak are XP boxes).
Have you managed to get gdb running on that box, and if so, can you try to grab a stacktrace? If not, try a stacktrace from process explorer. It doesn't actually work with mingw, but it gives you a hint based on DLL exports... //Magnus -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
