[9357] in The GTK GIMP ToolKit mailing list archive
[gtk-list] Re: Dumping core on SIGSEGV
daemon@ATHENA.MIT.EDU (Jason A. Pfeil)
Fri Oct 16 15:38:43 1998
Date: Fri, 16 Oct 1998 15:38:03 -0400 (EDT)
From: "Jason A. Pfeil" <pfeil@nu.cs.fsu.edu>
To: gtk-list@redhat.com
In-Reply-To: <19981016122730.E5124@linux.ataman.com>
Resent-From: gtk-list@redhat.com
Reply-To: gtk-list@redhat.com
Ah. :) Sorry. I misread the question. I think you can override that by
resetting the SEGV signal handler like this:
signal(SIGSEGV, SIG_DFL);
after the gtk_init is called.
--Jason
On Fri, 16 Oct 1998 beach@ataman.com wrote:
> 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
>
>
-------------------------------------------------------------------------------
Jason A. Pfeil, Computer Science Graduate Student 101 Carothers Hall
http://www.cs.fsu.edu/~pfeil C3527 University Center
pfeil@cs.fsu.edu (850)644-8014
--
To unsubscribe: mail -s unsubscribe gtk-list-request@redhat.com < /dev/null
