[9355] 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 15:11:20 1998
Date: Fri, 16 Oct 1998 13:06:36 -0600
From: beach@ataman.com
To: Gtk-List <gtk-list@redhat.com>
Mail-Followup-To: Gtk-List <gtk-list@redhat.com>
In-Reply-To: <19981016115844.B7473@shell9.ba.best.com>; from Brandon Long on Fri, Oct 16, 1998 at 11:58:44AM -0700
Resent-From: gtk-list@redhat.com
Reply-To: gtk-list@redhat.com
On Fri, Oct 16, 1998 at 11:58:44AM -0700, Brandon Long wrote:
> 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.
This signal handling mechanism doesn't seem appropriate to me. I
mean, what business does Gtk have with defining these kinds of
handlers? Shouldn't it be the job of the application to define these
things? Would it be possible to have this functionality set at
run-time instead of compile-time?
Dave
--
David J. C. Beach <beach@ataman.com>
Ataman Software, Inc.
--
To unsubscribe: mail -s unsubscribe gtk-list-request@redhat.com < /dev/null
