gdk_signal() is not useful

[Andy Kahn <kahn zk3 dec com>]

in trying to do some debugging, i wanted to find out why my
gtk program was not dumping core.  instead, it would print
something like:

** ERROR **: sigsegv caught


but no core file was generated (which is what i want).  without
defining "G_ENABLE_DEBUG", gdk_signal() does nothing beyond
calling "gdk_exit()", in turn which does nothing besides exit().

on the other hand, defining "G_ENABLE_DEBUG" causes gdk_signal()
to call abort(), but this can be misleading because it generates
*another* signal to end the current process.

what's the rationale for trying to catch fatal signals if the
routine isn't going to do anything useful about it?  i'd rather
have it core dump on me the first time around so i can go
debug the core instead of it printing something i would find
out anyway.
--andy