From: wahjava.ml@gmail.com (Ashish SHUKLA)
To: emacs-devel@gnu.org
Subject: Emacs segfaulting on FreeBSD 9.1-RELEASE (amd64) during bootstrap
Date: Wed, 03 Jul 2013 21:42:43 +0530 [thread overview]
Message-ID: <86txkb1v2c.fsf@chateau.d.if> (raw)
[-- Attachment #1: Type: text/plain, Size: 2218 bytes --]
Hi,
I tried bzr revision r113270 on my FreeBSD 9.1-RELEASE (amd64), and it
segfaulted during bootstrap process, (the compilation of files in "lisp"
directory). It generated a core-file lisp/bootstrap-emacs.core which has more
than 3-million (that's when I lost patience) recurring stack frames like
following:
#v+
#3367385 0x00000008080742c6 in pthread_mutex_lock () from /lib/libthr.so.3
#3367386 0x000000000066d846 in _malloc_internal (size=1016) at gmalloc.c:901
#3367387 0x000000000066d8c1 in malloc (size=1016) at gmalloc.c:925
#3367388 0x000000000066ec30 in calloc (nmemb=1, size=1016) at gmalloc.c:1492
#3367389 0x00000008080764bd in ?? () from /lib/libthr.so.3
#3367390 0x0000000808076d5b in ?? () from /lib/libthr.so.3
#3367391 0x00000008080742c6 in pthread_mutex_lock () from /lib/libthr.so.3
#3367392 0x000000000066d846 in _malloc_internal (size=1016) at gmalloc.c:901
#3367393 0x000000000066d8c1 in malloc (size=1016) at gmalloc.c:925
#3367394 0x000000000066ec30 in calloc (nmemb=1, size=1016) at gmalloc.c:1492
#3367395 0x00000008080764bd in ?? () from /lib/libthr.so.3
#3367396 0x0000000808076d5b in ?? () from /lib/libthr.so.3
#3367397 0x00000008080742c6 in pthread_mutex_lock () from /lib/libthr.so.3
#3367398 0x000000000066d846 in _malloc_internal (size=1016) at gmalloc.c:901
#3367399 0x000000000066d8c1 in malloc (size=1016) at gmalloc.c:925
#3367400 0x000000000066ec30 in calloc (nmemb=1, size=1016) at gmalloc.c:1492
#3367401 0x00000008080764bd in ?? () from /lib/libthr.so.3
#v-
Following is the configure line I used:
./configure --localstatedir=/var --with-x-toolkit=gtk3 --with-xft
--with-m17n-flt --with-libotf --with-imagemagick --with-gsettings
--with-gconf --with-xim --with-sound --with-dbus --with-xml2
--with-gnutls --with-acl --with-file-notification=gfile
--x-libraries=/usr/local/lib --x-includes=/usr/local/include
--prefix=/usr/local --mandir=/usr/local/man --infodir=/usr/local/info/
--build=amd64-portbld-freebsd9.1
Please let me know if you need more information from the core file.
Thanks
--
Ashish SHUKLA
”The only things certain in life are death, taxes, and accidentally deleted
data.” (bazza)
Sent from my Emacs
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2013-07-03 16:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 16:12 Ashish SHUKLA [this message]
2013-07-03 16:48 ` Emacs segfaulting on FreeBSD 9.1-RELEASE (amd64) during bootstrap Eli Zaretskii
2013-07-03 17:43 ` Ashish SHUKLA
2013-07-03 18:52 ` Eli Zaretskii
2013-07-03 19:04 ` Glenn Morris
2013-07-03 23:07 ` Giorgos Keramidas
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=86txkb1v2c.fsf@chateau.d.if \
--to=wahjava.ml@gmail.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).