From: Damien Deville <damien.deville@netasq.com>
To: emacs-devel@gnu.org
Subject: emacs-unicode-2 bootstrap on FreeBSD (temacs coredump)
Date: Fri, 27 Jul 2007 18:05:17 +0200 [thread overview]
Message-ID: <46AA17BD.7080900@netasq.com> (raw)
Hi emacs-devel,
On FreeBSD 6.2 with an up to date checkout of emacs-unicode-2 CVS temacs
coredump while bootstraping.
`/bin/pwd`/temacs --batch --load loadup bootstrap
Segmentation fault (core dumped)
gmake[2]: *** [bootstrap-emacs] Error 139
Launching gdb on the core shows the following trace:
(gdb) bt
#0 0x28a007a0 in pthread_once () from /lib/libpthread.so.2
#1 0x081a6ea1 in __malloc_initialize () at gmalloc.c:615
#2 0x081a6ed1 in malloc (size=68) at gmalloc.c:969
#3 0x28a00c0d in pthread_mutex_init () from /lib/libpthread.so.2
#4 0x28a00daf in _pthread_mutex_init () from /lib/libpthread.so.2
#5 0x28a0a8a5 in pthread_setconcurrency () from /lib/libpthread.so.2
#6 0x28a045be in _pthread_mutex_lock () from /lib/libpthread.so.2
#7 0x28a007ca in pthread_once () from /lib/libpthread.so.2
#8 0x081a6ea1 in __malloc_initialize () at gmalloc.c:615
#9 0x081a6ed1 in malloc (size=68) at gmalloc.c:969
#10 0x28a00c0d in pthread_mutex_init () from /lib/libpthread.so.2
#11 0x28a00daf in _pthread_mutex_init () from /lib/libpthread.so.2
#12 0x28a0a8a5 in pthread_setconcurrency () from /lib/libpthread.so.2
#13 0x28a045be in _pthread_mutex_lock () from /lib/libpthread.so.2
#14 0x28a007ca in pthread_once () from /lib/libpthread.so.2
#15 0x081a6ea1 in __malloc_initialize () at gmalloc.c:615
#16 0x081a6ed1 in malloc (size=68) at gmalloc.c:969
#17 0x28a00c0d in pthread_mutex_init () from /lib/libpthread.so.2
#18 0x28a00daf in _pthread_mutex_init () from /lib/libpthread.so.2
#19 0x28a0a8a5 in pthread_setconcurrency () from /lib/libpthread.so.2
#20 0x28a045be in _pthread_mutex_lock () from /lib/libpthread.so.2
#21 0x28a007ca in pthread_once () from /lib/libpthread.so.2
#22 0x081a6ea1 in __malloc_initialize () at gmalloc.c:615
---Type <return> to continue, or q <return> to quit---
The rest of the backtrace contains the same recursive call to
__malloc_initialize()
Thanks in advance,
Damien
next reply other threads:[~2007-07-27 16:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 16:05 Damien Deville [this message]
2007-07-29 10:13 ` emacs-unicode-2 bootstrap on FreeBSD (temacs coredump) Jan Djärv
2007-07-31 19:09 ` Herbert J. Skuhra
2007-08-01 8:46 ` YAMAMOTO Mitsuharu
2007-08-01 9:20 ` Jan Djärv
2007-08-01 9:35 ` YAMAMOTO Mitsuharu
2007-08-01 10:07 ` YAMAMOTO Mitsuharu
2007-08-01 10:42 ` YAMAMOTO Mitsuharu
2007-08-01 11:53 ` Jan Djärv
2007-08-01 11:54 ` Jan Djärv
2007-08-01 14:38 ` Miles Bader
2007-08-01 18:27 ` Jan D.
2007-08-06 8:47 ` YAMAMOTO Mitsuharu
2007-08-06 10:04 ` YAMAMOTO Mitsuharu
2007-08-06 18:17 ` Herbert J. Skuhra
2007-08-06 21:09 ` Ryan Yeske
2007-08-07 8:05 ` Jan Djärv
2007-08-07 9:22 ` YAMAMOTO Mitsuharu
2007-08-01 11:52 ` Jan Djärv
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=46AA17BD.7080900@netasq.com \
--to=damien.deville@netasq.com \
--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 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).