From: Chong Yidong <cyd@stupidchicken.com>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: crash: x_error_quitter
Date: Sun, 13 May 2007 09:52:10 -0400 [thread overview]
Message-ID: <87646whlv9.fsf@stupidchicken.com> (raw)
In-Reply-To: <46470BEF.4080107@swipnet.se> ("Jan Djärv"'s message of "Sun\, 13 May 2007 15\:00\:31 +0200")
Jan Djärv <jan.h.d@swipnet.se> writes:
>>> The reason we make this crash is so we can find the causes and fix them.
>>
>> Except I don't think we've found a single legitimate bug this way.
>
> Yes we have.
>
>> Every time this comes up, we just end up adding yet another call to
>> x_catch_error. Since X "protocol errors" are really more like warning
>> messages (as opposed to X "fatal errors"), I don't envision any other
>> situation cropping up.
>
> Depends on the error. Some are really fatal.
>
>> But hey, CPU cycles are cheap these days, so what does it matter if we
>> plaster unnecessary x_catch_error calls all over the code.
>
> It can hide a real error that causes the protocol error in the first place.
What's wrong with spitting out an error message to the terminal and
trying to continue, as I believe other X programs do?
next prev parent reply other threads:[~2007-05-13 13:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-10 18:05 crash: x_error_quitter sds
2007-05-11 18:48 ` Richard Stallman
2007-05-11 18:56 ` Sam Steingold
2007-05-12 16:47 ` Richard Stallman
2007-05-11 20:02 ` Chong Yidong
2007-05-12 6:51 ` Jan Djärv
2007-05-12 16:47 ` Richard Stallman
2007-05-12 23:31 ` Chong Yidong
2007-05-12 23:36 ` Chong Yidong
2007-05-13 13:29 ` Jan Djärv
2007-05-13 13:41 ` Chong Yidong
2007-05-13 13:00 ` Jan Djärv
2007-05-13 13:52 ` Chong Yidong [this message]
2007-05-13 15:33 ` Jan Djärv
2007-05-14 8:09 ` Richard Stallman
2007-05-14 8:40 ` David Kastrup
2007-05-15 9:47 ` Richard Stallman
2007-05-15 9:59 ` David Kastrup
2007-05-16 1:39 ` Richard Stallman
2007-05-16 6:58 ` David Kastrup
2007-05-16 14:32 ` Richard Stallman
2007-05-16 18:04 ` Eli Zaretskii
2007-05-16 21:42 ` David Kastrup
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87646whlv9.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=jan.h.d@swipnet.se \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).