This is the mail archive of the
mailing list for the Cygwin project.
Re: [PATCH] Add minidump write utility
- From: Jon TURNEY <jon dot turney at dronecode dot org dot uk>
- To: cygwin-patches <cygwin-patches at cygwin dot com>
- Date: Sat, 08 Feb 2014 15:00:18 +0000
- Subject: Re: [PATCH] Add minidump write utility
- Authentication-results: sourceware.org; auth=none
- References: <52F50B71 dot 8030608 at dronecode dot org dot uk>
On 07/02/2014 16:36, Jon TURNEY wrote:
> This patch adds a 'minidumper' utility, which functions identically to
> 'dumper' except it writes a Windows minidump, rather than a core file.
> I'm not sure if this is of use to anyone but me, but since I've had the patch
> sitting around for a couple of years, here it is...
> 2014-02-07 Jon TURNEY <firstname.lastname@example.org>
> * minidumper.cc: New file.
> * Makefile.in (CYGWIN_BINS): Add minidumper.
> * utils.xml (minidumper): New section.
Unfortunately there seems to be a bit of a problem with this patch. It seems
that cygwin assumes that the JIT debugger will terminate the debugged process.
I'm not sure if that's always been the case.
Consider the following test case:
$ cat segv-test.c
int main(int argc, char *argv)
*(char *)0 = 0;
$ gcc -o segv-test.exe segv-test.c
$ export CYGWIN="error_start:C:\cygwin\bin\true.exe"
seg-test crashes, true runs and exits, and segv-test spins.
dumper.exe does terminate the debugeee, but despite what utils.xml says about
this, I don't think this hasn't been a Windows API limitation since
DebugSetProcessKillOnExit() has existed.
I could fix this by making minidumper also terminate the dumped process, but
that doesn't seem the right approach.
I don't understand what debugging scenarios the waitloop part of
exceptions.cc:try_to_debug() is useful in, or why it doesn't wait until the
debugger process exits, so it's not clear to me how to fix this there, but
I'll note in passing that it seems that the thread's original priority is not
restored after running the debugger if waitloop=false, so perhaps at least the
following is needed:
--- cygwin/exceptions.cc 8 Jan 2014 16:51:20 -0000 1.432
+++ cygwin/exceptions.cc 8 Feb 2014 14:49:59 -0000
@@ -504,10 +504,8 @@
system_printf ("Failed to start debugger, %E");
+ else if (waitloop)
- if (!waitloop)
- return dbg;
SetThreadPriority (GetCurrentThread (), THREAD_PRIORITY_IDLE);
while (!being_debugged ())