unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: kbrown@cornell.edu, emacs-devel@gnu.org
Subject: Re: Dumper issue, revisited; invalid realloc/free
Date: Wed, 4 Feb 2015 23:33:18 -0500	[thread overview]
Message-ID: <20150205043317.GH23507@brightrain.aerifal.cx> (raw)
In-Reply-To: <83a90tf27l.fsf@gnu.org>

On Thu, Feb 05, 2015 at 05:48:30AM +0200, Eli Zaretskii wrote:
> > Date: Wed, 4 Feb 2015 22:25:50 -0500
> > From: Rich Felker <dalias@libc.org>
> > Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
> > 
> > with current git master I'm hitting lots of lisp failures later in
> > the build process, seemingly due to failure of autoloads to work,
> > although some of the failures don't even seem to be mentioned in
> > autoload.el. Is this kind of failure expected working with bleeding
> > edge (if so I'll seek support somewhere more appropriate), or does
> > it sound like something went wrong in dumping?
> 
> It's not expected, so you should debug it.

Thanks for steering me in the right direction. The problem was a mix
of two things:

1. I was having to incrementally increase the static sbrk size and
   still never getting enough because I didn't realize unexelf.c
   lacked code to set DUMPED to 1.

2. The failed bootstrap in lisp/ tree was leaving around stale/broken
   elc files that needed to be cleaned with "make bootstrap-clean".

I now have a working build with no ugly hackery. I'll share my patches
(mostly uninteresting) with the people doing dist packaging and see if
they can make something suitable for upstream.

Rich



  reply	other threads:[~2015-02-05  4:33 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-04 17:57 Dumper issue, revisited; invalid realloc/free Rich Felker
2015-02-04 19:08 ` Eli Zaretskii
2015-02-04 19:13   ` Rich Felker
2015-02-04 19:22     ` Eli Zaretskii
2015-02-04 19:26     ` Eli Zaretskii
2015-02-04 20:34       ` Ken Brown
2015-02-05  1:31         ` Rich Felker
2015-02-05  3:25           ` Rich Felker
2015-02-05  3:48             ` Eli Zaretskii
2015-02-05  4:33               ` Rich Felker [this message]
2015-02-05 16:14                 ` Wolfgang Jenkner
2015-02-05 18:43                   ` Rich Felker
2015-02-04 19:21 ` Eli Zaretskii
2015-02-04 19:37   ` Rich Felker
2015-02-04 19:44     ` Eli Zaretskii
2015-02-04 19:49       ` Rich Felker
2015-02-04 19:54         ` Eli Zaretskii
2015-02-04 20:02           ` Rich Felker
2015-02-04 20:36             ` Eli Zaretskii
2015-02-04 20:08       ` Rich Felker
2015-02-04 20:40         ` Eli Zaretskii
2015-02-04 22:17           ` Rich Felker
2015-02-05  3:42             ` Eli Zaretskii

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=20150205043317.GH23507@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=kbrown@cornell.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 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).