>>>> "GE" == Gunnar Evermann
<ge204(a)eng.cam.ac.uk> writes:
GE> If you start xemacs under gdb's control (as opposed to using gdb
GE> post-mortem to analyse the core dump)
that's exactly what I'm doing, i.e.:
gdb `which xemacs`
run
continue
<windows pop up, start vm, etc. etc.>
GE> then you'll get the gdb prompt back as soon as the fatal signal
GE> (ABORT, SEGV,...) is generated, before our signal handler (which
GE> in due course would generate the lisp backtrace) is called. You
GE> can get the lisp backtrace by either continuing execution from gdb
GE> or by calling 'lbt' if you use our .gdbinit.
ah, maybe that's the problem... I get the crash, do a where to get the
C stack, see there's nothing in the term window, and just hit run
again, rather than continuing...
sorry to be so dense about this, but xemacs is a different beast from
the stuff I usually debug...
-JT