From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: cyd@stupidchicken.com, emacs-devel@gnu.org
Subject: Re: unexec problem
Date: Tue, 05 Feb 2008 22:06:06 +0200 [thread overview]
Message-ID: <uabmftbgx.fsf@gnu.org> (raw)
In-Reply-To: <E1JMIn3-0007Zh-Da@fencepost.gnu.org> (message from Richard Stallman on Tue, 05 Feb 2008 03:04:25 -0500)
> From: Richard Stallman <rms@gnu.org>
> Date: Tue, 05 Feb 2008 03:04:25 -0500
> Cc: emacs-devel@gnu.org
>
> > When I try to bootstrap, bootstrap-emacs crashes
> > in the first call to malloc. Experience shows this is
> > usually due to a bug in the unexec mechanism.
> > However, unexelf.c is unchanged from Emacs 22.
> >
> > Since this sort of thing is a big pain to debug,
> > does anyone have any clues?
>
> Is this on the trunk?
>
> Yes. And it worked a week ago.
> I think the unicode merge broke it.
Probably.
How about running the bootstrap temacs (the one that is dumped to
produce bootstrap-emacs) under GDB with a breakpoint in malloc, and
recording all calls to malloc with their callers? Then you could
compare that with a similar run for a pre-merge CVS, and look for some
callers that could potentially lead to corruption of the malloc chain
the the dumped executable.
next prev parent reply other threads:[~2008-02-05 20:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-04 17:22 unexec problem Richard Stallman
2008-02-04 21:23 ` Chong Yidong
2008-02-05 8:04 ` Richard Stallman
2008-02-05 20:06 ` Eli Zaretskii [this message]
2008-02-06 16:12 ` Richard Stallman
2008-02-06 19:26 ` Eli Zaretskii
2008-02-08 4:15 ` Richard Stallman
2008-02-08 15:20 ` Eli Zaretskii
2008-02-10 18:42 ` Richard Stallman
2008-02-10 19:58 ` Eli Zaretskii
2008-02-11 13:35 ` Richard Stallman
2008-02-06 16:51 ` Dan Nicolaescu
2008-02-07 0:44 ` 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
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=uabmftbgx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@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 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).