[9358] in The GTK GIMP ToolKit mailing list archive
[gtk-list] Re: Dumping core on SIGSEGV
daemon@ATHENA.MIT.EDU (Blake)
Fri Oct 16 15:48:12 1998
From: Blake <laertes@stab.gemma.com>
To: gtk-list@redhat.com
Date: Mon, 16 Oct 100 14:52:43 -0600 (GMT+6)
In-Reply-To: <19981016130636.F5124@linux.ataman.com> from "beach@ataman.com" at Oct 16, 98 01:06:36 pm
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
>
Maybe a few miscelaneous Gtk functions can be called before gtk_init() to
determin it's behavior. After all, some applications might want/need default
ones like provided.
--Blake
--
To unsubscribe: mail -s unsubscribe gtk-list-request@redhat.com < /dev/null
