From: "Tim Van Holder" <tim.vanholder@gmail.com>
To: "Jason Rumney" <jasonr@gnu.org>
Cc: emacs-pretest-bug@gnu.org
Subject: Re: current CVS build segfaults
Date: Wed, 3 Oct 2007 16:20:18 +0200 [thread overview]
Message-ID: <d69e7f6a0710030720y2a3261bi4fce2b8ebac4314c@mail.gmail.com> (raw)
In-Reply-To: <47035C31.8030500@gnu.org>
On 10/3/07, Jason Rumney <jasonr@gnu.org> wrote:
> Tim Van Holder wrote:
> > The current CVS build segfaults during startup (with or without -q); stack trace in attachment (to avoid line break issues).
> >
> > (Note: the archives for this list seem to end in August, so I cannot check if this has been reported already; apologies if it is a duplicate entry)
> >
>
> emacs-pretest-bug was merged with emacs-devel in August, so subsequent
> messages are archived in emacs-devel. There is a mail from earlier today
> which includes a suggested fix for this bug. The subject is "GC crash".
I can confirm that this patch fixes the crash:
--- frame.h 03 Oct 2007 09:20:59 +0200 1.124
+++ frame.h 03 Oct 2007 16:10:39 +0200
@@ -78,7 +78,6 @@ struct frame
struct Lisp_Vector *next;
/* All Lisp_Object components must come first.
- Only EMACS_INT values can be intermixed with them.
That ensures they are all aligned normally. */
/* Name of this frame: a Lisp string. It is used for looking up resources,
@@ -152,8 +151,6 @@ struct frame
For the format of the data, see extensive comments in xmenu.c.
Only the X toolkit version uses this. */
Lisp_Object menu_bar_vector;
- /* Number of elements in the vector that have meaningful data. */
- EMACS_INT menu_bar_items_used;
/* Predicate for selecting buffers for other-buffer. */
Lisp_Object buffer_predicate;
@@ -183,6 +180,9 @@ struct frame
/* Cache of realized faces. */
struct face_cache *face_cache;
+ /* Number of elements in the vector that have meaningful data. */
+ EMACS_INT menu_bar_items_used;
+
/* A buffer to hold the frame's name. We can't use the Lisp
string's pointer (`name', above) because it might get relocated. */
char *namebuf;
Note that putting anything before face_cache still triggers the
segfault (because face_cache is explicitly used in alloc.c to decide
the pseudovector's size), so perhaps an additional comment to that
effect is needed as well.
next prev parent reply other threads:[~2007-10-03 14:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-03 8:45 current CVS build segfaults Tim Van Holder
2007-10-03 9:09 ` Jason Rumney
2007-10-03 14:20 ` Tim Van Holder [this message]
2007-10-03 15:20 ` dhruva
-- strict thread matches above, loose matches on Subject: below --
2007-10-03 17:42 Robert J. Chassell
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=d69e7f6a0710030720y2a3261bi4fce2b8ebac4314c@mail.gmail.com \
--to=tim.vanholder@gmail.com \
--cc=emacs-pretest-bug@gnu.org \
--cc=jasonr@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).