all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Joe Wells <jbw@macs.hw.ac.uk>
To: Eli Zaretskii <eliz@gnu.org>
Cc: bug-gnu-emacs@gnu.org, rms@gnu.org
Subject: Re: Emacs exited with message “X protocol error: BadPixmap”
Date: Mon, 13 Aug 2007 21:41:42 +0100	[thread overview]
Message-ID: <86odhbdv5l.fsf@macs.hw.ac.uk> (raw)
In-Reply-To: <u7inzdxxv.fsf@gnu.org> (Eli Zaretskii's message of "Mon\, 13 Aug 2007 22\:41\:32 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Joe Wells <jbw@macs.hw.ac.uk>
>> Date: Mon, 13 Aug 2007 06:20:53 +0100
>> Cc: bug-gnu-emacs@gnu.org
>> 
>> Sorry, I'm not going to run Emacs under GDB indefinitely just on the
>> off chance Emacs will crash.
>
> Why not?  As long as Emacs doesn't crash, you will not notice any
> difference in behavior or performance--GDB is simply invisible until
> there's some event that is noteworthy for the debugger.

I'm not going to run every program on my system under the debugger
forevermore on the off chance that the program might crash!

-- 
Joe

>> I depend on programs to leave core dump files when they crash.
>
> Debugging a core file has limitations that debugging a live program
> (even if it crashed) does not.  Some of the GDB features do not work
> with core files.

  reply	other threads:[~2007-08-13 20:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-12  1:20 Emacs exited with message “X protocol error: BadPixmap” Joe Wells
2007-08-12 17:56 ` Richard Stallman
2007-08-12 18:17   ` Joe Wells
2007-08-13  5:01     ` Richard Stallman
2007-08-13  5:20       ` Joe Wells
2007-08-13 19:41         ` Eli Zaretskii
2007-08-13 20:41           ` Joe Wells [this message]
2007-08-14  0:28             ` Richard Stallman
2007-08-14  8:27               ` Kim F. Storm
2007-08-14 19:23                 ` Eli Zaretskii
2007-08-14 23:26                 ` Richard Stallman
2007-08-14  3:07             ` Eli Zaretskii
2007-08-14  0:27         ` Richard Stallman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86odhbdv5l.fsf@macs.hw.ac.uk \
    --to=jbw@macs.hw.ac.uk \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=eliz@gnu.org \
    --cc=rms@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.