--- Begin Message ---
|
Subject: |
24.3.50; bootstrap failed; bootstrap-emacs segfaults |
|
Date: |
Tue, 19 Feb 2013 09:06:37 +0900 |
|
User-agent: |
Gnus/5.130006 (真 Gnus v0.6) Emacs/24.3.50 (i686-pc-cygwin) |
In GNU Emacs 24.3.50.1 (i686-pc-cygwin, X toolkit, Xaw3d scroll bars)
of 2013-02-15 on localhost
(Bzr revision: 111784 address@hidden)
Windowing system distributor `The Cygwin/X Project', version 11.0.11302000
Configured using:
`configure --verbose --with-x-toolkit=lucid --without-imagemagick
--without-dbus --without-gconf --without-gsettings'
Can't build Emacs trunk on Cygwin (daily updated) on Windows 7:
[...]
Static heap usage: 9541024 of 13631488 bytes
43466 pure bytes used
cd ../lisp; make -w compile-first EMACS=/Work/emacs/src/bootstrap-emacs.exe
make[3]: Entering directory `/Work/emacs/lisp'
Compiling /Work/emacs/lisp/emacs-lisp/macroexp.el
Fatal error 11: Segmentation faultMakefile:243:\
recipe for target `/Work/emacs/lisp/emacs-lisp/macroexp.elc' failed
Here's a backtrace:
% gdb src/bootstrap-emacs.exe
GNU gdb (GDB) 7.5.50.20120815-cvs (cygwin-special)
[...]
Reading symbols from /Work/emacs/src/bootstrap-emacs.exe...done.
(gdb) r
Starting program: /Work/emacs/src/bootstrap-emacs.exe
[New Thread 9364.0x1a3c]
[New Thread 9364.0x1d18]
Program received signal SIGSEGV, Segmentation fault.
mmap_alloc (var=0xf26d18, nbytes=15273) at buffer.c:4906
4906 r->next->prev = r;
(gdb) bt
#0 mmap_alloc (var=0xf26d18, nbytes=15273) at buffer.c:4906
#1 0x004d07b9 in mmap_realloc (nbytes=15273, var=0xf26d18) at buffer.c:4945
#2 enlarge_buffer_text (b=0xf26c00, delta=0) at buffer.c:5053
#3 0x004d1e16 in init_buffer () at buffer.c:5301
#4 0x004af6dd in main (argc=1, argv=0x22ac40) at emacs.c:1305
(gdb)
Is any other information required? Thanks.
--- End Message ---
--- Begin Message ---
|
Subject: |
Re: bug#13759: 24.3.50; bootstrap failed; bootstrap-emacs segfaults |
|
Date: |
Wed, 20 Feb 2013 19:19:09 +0900 |
|
User-agent: |
Gnus/5.130006 (真 Gnus v0.6) Emacs/24.3.50 (i686-pc-cygwin) |
Daniel Colascione wrote:
[...]
> Anyway, I've installed the following patch to trunk, which
> fixes the problem. If we want to go back to using message1,
> let's somehow make sure it doesn't log.
Thanks a lot! It enables me to play with ELisp again.
--- End Message ---