[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Emacs exited with message “X protocol error: BadPixmap”

From: Kim F. Storm
Subject: Re: Emacs exited with message “X protocol error: BadPixmap”
Date: Tue, 14 Aug 2007 10:27:23 +0200
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux)

Richard Stallman <address@hidden> writes:

>     I'm not going to run every program on my system under the debugger
>     forevermore on the off chance that the program might crash!
> Why not?  Do you feel it would be unethical?

I mostly run emacs under a debugger - but not every time, as
it is not always practical to do so.

E.g. when emacs is started through a desktop shortcut or launced by
some other program (like through the emacs.bash script distributed
with Emacs), there's no debugger involved ... and sometimes I just
continue working in such an Emacs instance ... without the debugger
in place.

Anyways, I've seen on Windoze that if Emacs crashes, Visual Studio
kicks in and offers you to debug the crashed process.

Can't Emacs be taught to do something similar by hooking various
signal handlers (SIGSEGV, SIGILL, etc) to a function that launches GDB
with command line parameters that attaches it to the (crashed) Emacs
runtime?  That way, GDB is only started _if_ Emacs crashes.

This could be a configuration option `debug-on-crash' with these values:

- nil, meaning don't debug, just dump core and crash
- t, meaning launch gdb unconditionally
- ask, meaining ask user to launch gdb or dump core

Kim F. Storm <address@hidden> http://www.cua.dk

reply via email to

[Prev in Thread] Current Thread [Next in Thread]