From: Jason Rumney <jasonr@gnu.org>
To: Chris Hall <cjh@insidernewswire.com>
Cc: Emacs bugs <bug-gnu-emacs@gnu.org>, Dan Nicolaescu <dann@ics.uci.edu>
Subject: Re: 23.0.60; Seg fault in xfaces.c at line 6703 (Emacs.app on GNUstep)
Date: Mon, 04 Feb 2008 08:47:12 +0000 [thread overview]
Message-ID: <47A6D110.2010206@gnu.org> (raw)
In-Reply-To: <5c3f50e8df2b05f7f2e7b1843d425e14@lagorda>
Chris Hall wrote:
> On 2008-02-03 10:52:46 -1000 Jason Rumney <jasonr@gnu.org> wrote:
>
>> If it is a bug to have 0 in that field, why would you hide the bug by
>> avoiding a crash when it is 0?
>
> So it could terminate gracefully while reporting that it had a 0 in
> that field, along with any other available information that might
> prove useful in helping to solve the problem? Maybe offer to run in
> text mode with that information made available in a buffer with a bug
> report?
>
> I didn't mention anything about 'hiding' it, did I?
>
> With the patch I supplied, at least the user knows there is an issue
> with realizing the default face, rather than SIGSEGV (11).
Since this is a programming error in an internal structure, in a
development version of the code, it is letting the developer know there
is an error. Developers have debuggers, they don't need code to catch
bugs and exit gracefully. To write code to catch every potential NULL
pointer exception in the internal structures would make Emacs bloated
and slow.
next prev parent reply other threads:[~2008-02-04 8:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-02 3:51 23.0.60; Seg fault in xfaces.c at line 6703 (Emacs.app on GNUstep) Chris
2008-02-02 20:13 ` Dan Nicolaescu
2008-02-03 7:20 ` Chris Hall
2008-02-03 17:19 ` Dan Nicolaescu
2008-02-04 1:39 ` YAMAMOTO Mitsuharu
2008-02-04 7:28 ` Chris Hall
2008-02-04 7:38 ` YAMAMOTO Mitsuharu
2008-02-04 9:55 ` Chris Hall
2008-02-04 10:15 ` William Xu
2008-02-04 10:57 ` YAMAMOTO Mitsuharu
2008-02-04 11:35 ` William Xu
2008-02-05 11:07 ` Chris Hall
2008-02-06 1:34 ` YAMAMOTO Mitsuharu
2008-02-06 9:53 ` Chris Hall
2008-02-05 13:30 ` Chris Hall
2008-02-03 20:52 ` Jason Rumney
2008-02-04 3:20 ` Chris Hall
2008-02-04 4:40 ` William Xu
2008-02-04 8:47 ` Jason Rumney [this message]
2008-02-04 10:32 ` Chris Hall
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=47A6D110.2010206@gnu.org \
--to=jasonr@gnu.org \
--cc=bug-gnu-emacs@gnu.org \
--cc=cjh@insidernewswire.com \
--cc=dann@ics.uci.edu \
/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.