Re: Help getting backtrace in gdb

[Davis Herring]

> # Don't enter GDB when user types C-g to quit.
> # This has one unfortunate effect: you can't type C-c
> # at the GDB to stop Emacs, when using X.
> # However, C-z works just as well in that case.
> handle 2 noprint pass

So how do you break back into the debugger?  C-z would just suspend gdb 
itself (and probably emacs if it is an inferior rather than an attached 
process)...

Davis

--
This product is sold by volume, not by mass.  If it appears too dense or 
too sparse, it is because mass-energy conversion has occurred during 
shipping.