[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Emacs exited with message “X protocol error: BadPixmap”
From: |
Joe Wells |
Subject: |
Re: Emacs exited with message “X protocol error: BadPixmap” |
Date: |
Sun, 12 Aug 2007 19:17:30 +0100 |
User-agent: |
Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) |
Richard Stallman <rms@gnu.org> writes:
> To debug an X protocol error, you need to do (x-synchronize t).
> That way xlib detects the error inside the primitive that failed.
> Normally it finds out about the error later on, inside
> some other primitive, so the backtrace is irrelevant to the cause
> of the error.
Thanks very much for this information!
>From reading the code, it is not clear whether this is enough to also
get core dump files from these errors. What would I need to do to
ensure that such a crash produced a core dump file?
--
Joe
- Emacs exited with message “X protocol error: BadPixmap”, Joe Wells, 2007/08/11
- Re: Emacs exited with message “X protocol error: BadPixmap”, Richard Stallman, 2007/08/12
- Re: Emacs exited with message “X protocol error: BadPixmap”,
Joe Wells <=
- Re: Emacs exited with message “X protocol error: BadPixmap”, Richard Stallman, 2007/08/13
- Re: Emacs exited with message “X protocol error: BadPixmap”, Joe Wells, 2007/08/13
- Re: Emacs exited with message “X protocol error: BadPixmap”, Eli Zaretskii, 2007/08/13
- Re: Emacs exited with message “X protocol error: BadPixmap”, Joe Wells, 2007/08/13
- Re: Emacs exited with message “X protocol error: BadPixmap”, Richard Stallman, 2007/08/13
- Re: Emacs exited with message “X protocol error: BadPixmap”, Kim F. Storm, 2007/08/14
- Re: Emacs exited with message “X protocol error: BadPixmap”, Eli Zaretskii, 2007/08/14
- Re: Emacs exited with message “X protocol error: BadPixmap”, Richard Stallman, 2007/08/14
- Re: Emacs exited with message “X protocol error: BadPixmap”, Eli Zaretskii, 2007/08/13
- Re: Emacs exited with message “X protocol error: BadPixmap”, Richard Stallman, 2007/08/13