[9352] in The GTK GIMP ToolKit mailing list archive
[gtk-list] Re: Dumping core on SIGSEGV
daemon@ATHENA.MIT.EDU (beach@ataman.com)
Fri Oct 16 14:30:53 1998
Date: Fri, 16 Oct 1998 12:27:30 -0600
From: beach@ataman.com
To: gtk-list@redhat.com
Mail-Followup-To: gtk-list@redhat.com
In-Reply-To: <Pine.GSO.4.05.9810161351350.5027-100000@xi>; from Jason A. Pfeil on Fri, Oct 16, 1998 at 01:52:22PM -0400
Resent-From: gtk-list@redhat.com
Reply-To: gtk-list@redhat.com
On Fri, Oct 16, 1998 at 01:52:22PM -0400, Jason A. Pfeil wrote:
> Ummm...if gtk DOESN'T catch SIGSEGV, then the core IS dumped. What seems
> to be the problem here? Signals are up to the application to catch
> anyway.
>
> --Jason
>
> On Fri, 16 Oct 1998 beach@ataman.com wrote:
>
> >
> > Why doesn't Gtk catch SIGSEGV instead of allowing a core dump? This
> > is making it difficult to use in development at times (e.g. no
> > coredump files to work with means nothing to give to the debugger.)
Please excuse my horribly phrased question. What I meant to say was:
Why *does* Gtk catch SIGSEGV. I'd like it to coredump so that I can
use the debugger. What should I do?
Dave
--
David J. C. Beach <beach@ataman.com>
Ataman Software, Inc.
--
To unsubscribe: mail -s unsubscribe gtk-list-request@redhat.com < /dev/null
