From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: bootstrap problem
Date: Fri, 26 May 2006 11:07:29 +0300 [thread overview]
Message-ID: <ud5e1i4zi.fsf@gnu.org> (raw)
In-Reply-To: <20060526134758.2944@henman-np.b-eng.it.to-be.co.jp>
> Cc: "djh" <henman@it.to-be.co.jp>, <emacs-devel@gnu.org>
> From: "djh" <henman@it.to-be.co.jp>
> Date: Fri, 26 May 2006 13:47:58 +0900
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x610ad945 in pthread_mutexattr_init () from /usr/bin/cygwin1.dll
So Emacs does, indeed, crash. However, your previous transcript
indicated it was a SIGABRT, not SIGSEGV:
> Fatal error (6)zsh: abort (core dumped) ./bootstrap-emacs.exe -batch --no-site-file --multibyte -f byte-opt.el
Signal 6 is SIGABRT, IIRC.
> (gdb) backtrace
> #0 0x610ad945 in pthread_mutexattr_init () from /usr/bin/cygwin1.dll
> #1 0x6108dd7f in _sigfe () from /usr/bin/cygwin1.dll
> #2 0x00000003 in ?? ()
> #3 0x0022ee18 in ?? ()
> #4 0x00000001 in ?? ()
> #5 0x0022ee18 in ?? ()
> #6 0x0022ee38 in ?? ()
> #7 0x200a2100 in main (argc=539893664, argv=0x4) at emacs.c:1062
Ouch! Was your Emacs compiled with "-gdwarf-2 -g3" compiler switches?
If not, please reconfigure to use these and rebuild. It will be very
hard to debug this without a reliable debug info. Also, please make
sure you have the latest version of GDB available under Cygwin. If
there's a version of cygwin1.dll with full debug info, please use that
as well in your next trials.
If none of the above helps to get a more meaningful backtrace, I'm
afraid you will need to ask on the Cygwin list for more help. We need
some way of getting a meaningful backtrace, to know where Emacs
crashes, and I don't know enough about Cygwin internals to suggest how
to get it, except with the above advice.
> Lisp Backtrace:
> 0x0 Lisp type 0
> Cannot access memory at address 0x0
>
> xbacktrace
> 0x0 Lisp type 0
> Cannot access memory at address 0x0
This is expected when C-level backtrace is garbled as above.
Thanks.
next prev parent reply other threads:[~2006-05-26 8:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-25 4:33 bootstrap problem djh
2006-05-25 18:26 ` Eli Zaretskii
2006-05-26 4:47 ` djh
2006-05-26 8:07 ` Eli Zaretskii [this message]
2006-05-30 7:03 ` cygwn 5.19 with X-win bootstrap djh
2006-05-30 19:19 ` Eli Zaretskii
2006-06-01 4:56 ` djh
2006-06-01 7:08 ` Eli Zaretskii
2006-06-02 9:03 ` djh
2006-06-02 9:27 ` Eli Zaretskii
2006-06-20 8:49 ` djh
-- strict thread matches above, loose matches on Subject: below --
2005-03-30 8:45 Bootstrap problem Lute Kamstra
2005-03-30 10:39 ` Kim F. Storm
2005-03-30 11:40 ` Lute Kamstra
2005-04-07 17:43 ` Lute Kamstra
2005-04-08 3:22 ` Richard Stallman
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=ud5e1i4zi.fsf@gnu.org \
--to=eliz@gnu.org \
--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).