Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
From:	"Doug Wyatt" <dwyatt AT sunflower DOT com>
To:	cygwin <cygwin AT cygwin DOT com>
Date:	Fri, 20 Sep 2002 03:50:44 -0500
MIME-Version:	1.0
Subject:	gdb segfaults with dumper core file
Reply-to:	dwyatt AT sunflower DOT com
Message-ID:	<3D8A9B14.6393.A709FAA@localhost>

Hi,

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 ...

Regards,
Doug Wyatt

Versions used are:
binutils            20020706-2
cygwin            1.3.12-4
gcc                 3.1.1-4
gdb                 20020718-1



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -