[9353] in The GTK GIMP ToolKit mailing list archive
[gtk-list] Re: Dumping core on SIGSEGV
daemon@ATHENA.MIT.EDU (Brandon Long)
Fri Oct 16 15:00:02 1998
Date: Fri, 16 Oct 1998 11:58:44 -0700
From: Brandon Long <blong@fiction.net>
To: Gtk-List <gtk-list@redhat.com>
Reply-To: blong@fiction.net
Mail-Followup-To: Gtk-List <gtk-list@redhat.com>
In-Reply-To: <19981016112540.D5124@linux.ataman.com>; from beach@ataman.com on Fri, Oct 16, 1998 at 11:25:40AM -0600
Resent-From: gtk-list@redhat.com
On 10/16/98 beach@ataman.com uttered the following other thing:
>
> 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.)
You can recompile gdk/gtk and edit gdk/gdk.c, the line:
/* If you don't want to use gdk's signal handlers define this */
/* #define I_NEED_TO_ACTUALLY_DEBUG_MY_PROGRAMS 1 */
Perhaps it would be good to make this set in some other way than a
compile time option? Either enable it with --debug or something.
I generally just run my application under gdb when I'm getting a
segfault, since gdb will grab the app when it happens and you can do a
backtrace, etc.
Brandon
--
Brandon Long "... a boy who gets a 'C-minus' in
MD6 Crash Test Dummy Appreciation of Televison can't be all bad."
Intel Corporation -- Robert Heinlein, _Starship Troopers_
I'm too low on the totem pole to speak for Intel.
http://www.fiction.net/blong/
--
To unsubscribe: mail -s unsubscribe gtk-list-request@redhat.com < /dev/null
