From: Eli Zaretskii <eliz@gnu.org>
To: Werner LEMBERG <wl@gnu.org>
Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org
Subject: Re: compilation failure
Date: Wed, 30 Mar 2011 07:25:09 -0400 [thread overview]
Message-ID: <E1Q4tWP-0007BM-Sb@fencepost.gnu.org> (raw)
In-Reply-To: <20110330.085238.150445611.wl@gnu.org> (message from Werner LEMBERG on Wed, 30 Mar 2011 08:52:38 +0200 (CEST))
> Date: Wed, 30 Mar 2011 08:52:38 +0200 (CEST)
> From: Werner LEMBERG <wl@gnu.org>
> Cc: emacs-devel@gnu.org
>
> LC_ALL=C ./temacs -batch -l loadup dump
>
> it aborts. Calling gdb, I get the backtrace shown below. Note that
> I'm doing a normal build without any additional options.
>
>
> Werner
>
>
> ======================================================================
>
> #0 mark_object (arg=138477574) at alloc.c:5429
> #1 0x08195d4e in mark_maybe_pointer (p=<optimized out>) at alloc.c:4083
> #2 mark_memory (offset=0, end=0xbfffed98, start=0x841313a) at alloc.c:4133
> #3 mark_stack () at alloc.c:4381
> #4 Fgarbage_collect () at alloc.c:4966
Can you try unoptimized build (with "-O0 -ggdb -g3")? If that crashes
as well, please show the backtrace from an unoptimized build, because
backtraces from optimized builds cannot be trusted.
Based on first glance, it crashes in GC, which means memory corruption
somewhere. There are instructions in etc/DEBUG about how to debug
crashes in GC, so if you can follow them, please do; since this crash
is not very deep under Fgarbage_collect, I presume you will find out
the bad data structure fairly easy.
Failing that, please leave the crashed Emacs under GDB, so that we
could ask you to show important values.
If an unoptimized build does not crash, then the plot will thicken...
Btw, what version of GCC do you have on Ubuntu 10.10?
next prev parent reply other threads:[~2011-03-30 11:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 6:13 compilation failure Werner LEMBERG
2011-03-30 6:31 ` Paul Eggert
2011-03-30 6:52 ` Werner LEMBERG
2011-03-30 7:42 ` Jim Meyering
2011-03-30 8:04 ` Werner LEMBERG
2011-03-30 11:37 ` Eli Zaretskii
2011-03-30 12:29 ` Werner LEMBERG
2011-03-30 11:35 ` Eli Zaretskii
2011-03-30 13:41 ` Jim Meyering
2011-03-30 18:16 ` Eli Zaretskii
2011-03-30 18:16 ` Eli Zaretskii
2011-03-30 11:25 ` Eli Zaretskii [this message]
2011-03-30 13:00 ` Werner LEMBERG
2011-03-30 18:17 ` Eli Zaretskii
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=E1Q4tWP-0007BM-Sb@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=wl@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).