all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Chris Hall <cjh@insidernewswire.com>
To: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
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: Sun, 03 Feb 2008 21:28:58 -1000	[thread overview]
Message-ID: <4ab48944a960527e5792ab6702c0f683@lagorda> (raw)
In-Reply-To: <wlwsplcxed.wl%mituharu@math.s.chiba-u.ac.jp>

> 
> As I said in *1, I could reproduce a similar backtrace by deliberately
> defining CANNOT_DUMP.  I suspect this is a generic problem for
> CANNOT_DUMP platforms after the multi-tty merger.
> 
> *1 http://lists.gnu.org/archive/html/emacs-devel/2008-01/msg02051.html
> 

Thank you for following up on this, I truly appreciate it, but that 
is, I believe, the separate (and earlier) thread concerning the 
'Vprocess_environment is not properly initialized on CANNOT_DUMP 
platforms' issue.

In this one they were explaining to me that the seg fault by 
attempting to reference a field in an uninitialized face_cache struct 
-- the initialized version of which is quite clearly a necessary 
prerequisite to realizing a face in the first place -- is not 
considered to be caused by a bug in Emacs 23.0.60 and that seg fault 
_should_ occur in this case.

IOW, a bug in Emacs.app seems to have left the face_cache struct 
uninitialized.

Perhaps a somewhat similar, 'face realization' issue in the Carbon 
version as well ( see 
http://lists.gnu.org/archive/html/bug-gnu-emacs/2008-02/msg00021.html 
).

And apparently this has started happening to both versions since the 
unicode merge?







  reply	other threads:[~2008-02-04  7:28 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 [this message]
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
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=4ab48944a960527e5792ab6702c0f683@lagorda \
    --to=cjh@insidernewswire.com \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=dann@ics.uci.edu \
    --cc=mituharu@math.s.chiba-u.ac.jp \
    /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.