Re: GDB cannot access memory after Emacs abort

Andreas Schwab
2007-11-13T23:57:08Z

Stephen Berman <Stephen.Berman@gmx.net> writes:

> After the abort occurs, the desktop locks up, I switch to a virtual tty
> and kill -9 the emacs process, releasing the desktop, then type what you
> said at the gdb prompt and get this:
>
> 0x80f9e56 <abort+6>: Cannot access memory at address 0x80f9e56

Of course, after forcefully killing the process it does not exist any
more, so there is nothing the debugger can inspect.

I'd suggest running the debugger inside screen, then you can attach to
the screen instance from any other tty and inspect the still running
emacs process.

Andreas.

--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, MaxfeldstraÃŸe 5, 90409 NÃ¼rnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."