From: Nick Roberts <nickrob@snap.net.nz>
Cc: emacs-devel@gnu.org
Subject: seg-fault in unexelf.c
Date: Sat, 22 Jul 2006 12:33:34 +1200 [thread overview]
Message-ID: <17601.29278.738547.379915@kahikatea.snap.net.nz> (raw)
In-Reply-To: <Pine.LNX.4.64.0607211342320.2372@localhost.localdomain>
> I have been having a problem building emacs on GNU/Linux (in
> particular, the Fedora Core 5 distribution). The build process runs
> the following command in the src/ subdirectory:
>
> ./temacs -l loadup -batch dump
>
> to cause the temacs binary (essentially emacs without the Lisp code
> loaded) to set up the Lisp environment in the process address space
> and then create a new ELF file with a new .data section that contains
> the .data and .bss sections from the temacs process.
>
> If I build the temacs binary with no compiler optimization (gcc (GCC)
> 4.1.0 20060304 (Red Hat 4.1.0-3)), the command above seg-faults in the
> unexec function (file unexelf.c) while executing this line:
>...
I regularly build on FC5 without optimization and don't have any problems
(although I haven't done "make bootstrap for a while, the final build uses
"./temacs -l loadup -batch dump").
gcc (GCC) 4.1.1 20060525 (Red Hat 4.1.1-1)
Linux kahikatea.snap.net.nz 2.6.15-1.2054_FC5 #1 Tue Mar 14 15:48:33 EST 2006 i686 i686 i386 GNU/Linux
n
In GNU Emacs 22.0.50.41 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
of 2006-07-21 on kahikatea.snap.net.nz
X server distributor `The X.Org Foundation', version 11.0.70000000
configured using `configure 'CFLAGS=-g3''
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2006-07-22 0:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-21 17:59 seg-fault in unexelf.c Chip Coldwell
2006-07-21 20:53 ` Chip Coldwell
2006-07-22 0:33 ` Nick Roberts [this message]
2006-07-22 12:37 ` Chip Coldwell
2006-07-22 12:50 ` Nick Roberts
2006-07-22 4:39 ` Richard Stallman
2006-07-22 12:27 ` Chip Coldwell
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=17601.29278.738547.379915@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=emacs-devel@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 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.