From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Re: Proposed Windows-specific change: Enable crash dumps (like core files) |
Date: | 2011-07-10 20:23:58 |
Message-ID: | 1310329438.11713.1.camel@vanquo.pezone.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On tor, 2010-12-16 at 15:16 +0100, Magnus Hagander wrote:
> Found another problem in it: when running with an older version of
> dbghelp.dll (which I was), it simply didn't work. We need to grab the
> version of dbghelp.dll at runtime and pick which things we're going to
> dump based on that.
>
> The attached version of the patch does that. Can you please test that
> it still generates the full dump on your system, which supposedly has
> a much more modern version of dbghelp.dll than mine?
I was going through the GetLastError() calls to unify the printf
formats, as discussed, and I stumbled across this:
+ write_stderr("could not write crash dump to %s: error code %08x\n",
+ dumpPath, GetLastError());
Is there a reason why this uses that particular format, unlike all other
call sites?
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2011-07-10 21:15:55 | Re: reducing the overhead of frequent table locks, v4 |
Previous Message | Brar Piening | 2011-07-10 19:46:33 | Re: Review of VS 2010 support patches |