This is the mail archive of the
mailing list for the Cygwin project.
gdb segfaults with dumper core file
- From: "Doug Wyatt" <dwyatt at sunflower dot com>
- To: cygwin <cygwin at cygwin dot com>
- Date: Fri, 20 Sep 2002 03:50:44 -0500
- Subject: gdb segfaults with dumper core file
- Reply-to: dwyatt at sunflower dot com
I've been unable to find much in the archives about the dumper.exe tool
and I'm almost as unfamiliar with gdb usage so ...
I've compiled a program called pcps, which converts text to postscript
and sends it to a printer. Under an admin login, it works pretty much
correctly. But, under a normal 'Domain Users' account it delivers the
job to the print spooler and then segfaults. The output does print.
Under gdb it runs without segfaulting... as any cynic would expect.
So, I modified cygwin.bat with the dumper.exe entry, reran pcps and
got a pcps.exe.core that is about 2MB in size. I tried a few variations
on 'gdb --core=pcps.exe.core' and gdb itself segfaults in every case
and generates a 'gdb.exe.core' of about 7MB.
Is there some trick to using dumper output with gdb? Or do I need
to resign myself to the recursive strategy of now debugging gdb,
and so on ...
Versions used are:
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html