From: Stephen Berman <Stephen.Berman@gmx.net>
To: gdb@sources.redhat.com
Subject: GDB cannot access memory after Emacs abort
Date: Sat, 10 Nov 2007 23:50:00 -0000 [thread overview]
Message-ID: <87hcjtllau.fsf@escher.local.home> (raw)
In-Reply-To: <87r6j6rvn3.fsf@escher.local.home>
I recently experienced an abort in CVS Emacs and was unable to get a
backtrace from GDB. The Emacs bug causing the abort was fixed, but
Richard Stallman responded to the lack of a backtrace with this comment:
> That could be a serious problem in GDB. It would be good to talk
> with GDB developers about how to investigate it. Since the bug's
> cause is known, they could focus on figuring out why GDB fails
> to give a backtrace.
Here is the GDB-relevant part of my bug report about the abort (Emacs
was built using the GTK+ toolkit):
> I attempted to debug in gdb; here's the output when the abort occurs:
>
> (emacs:19177): Gtk-WARNING **: Can't set a parent on widget which has a parent
>
>
> Gtk-ERROR **: file gtkcontainer.c: line 2641 (gtk_container_propagate_expose): assertion failed: (child->parent == GTK_WIDGET (container))
> aborting...
> [Switching to Thread 0xb6ec66c0 (LWP 19177)]
>
> Breakpoint 1, abort () at emacs.c:431
> 431 kill (getpid (), SIGABRT);
>
> At this point my desktop (I tried in KDE, GNOME and twm, same behavior
> in all) is totally locked up, but I can switch to a virtual tty and
> there kill emacs with SIGKILL (kill -9); SIGTERM (kill -15) does not do
> the job. This releases the desktop, but gdb delivers no further
> feedback:
>
> (gdb) xbacktrace
> Cannot access memory at address 0x8321b6c
> (gdb) bt
> #0 abort () at emacs.c:431
> Cannot access memory at address 0xbfd6836c
> Cannot access memory at address 0x8321b6c
>
> Setting a break point at abort() in emacs.c makes no difference. I
> don't have the GTK+ source code so I cannot debug it there.
Does anyone have an idea why there was no backtrace?
Steve Berman
next parent reply other threads:[~2007-11-10 23:50 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87r6j6rvn3.fsf@escher.local.home>
2007-11-10 23:50 ` Stephen Berman [this message]
2007-11-11 6:46 ` Michael Snyder
2007-11-11 7:44 ` Eli Zaretskii
2007-11-11 23:05 ` Stephen Berman
2007-11-12 4:18 ` Eli Zaretskii
2007-11-12 5:24 ` Michael Snyder
2007-11-13 22:40 ` Stephen Berman
2007-11-13 23:20 ` Michael Snyder
2007-11-13 23:28 ` Dan Nicolaescu
2007-11-14 10:00 ` Stephen Berman
2007-11-13 23:57 ` Andreas Schwab
2007-11-11 19:22 ` Daniel Jacobowitz
2007-11-11 23:10 ` Stephen Berman
2007-11-12 0:39 ` Daniel Jacobowitz
2007-11-12 17:47 ` Jim Blandy
2007-11-12 19:44 ` Andreas Schwab
2007-11-13 22:36 ` Stephen Berman
2007-11-13 22:34 ` Stephen Berman
2007-11-13 23:14 ` Michael Snyder
2007-11-14 9:48 ` Stephen Berman
2007-11-13 23:51 ` Andreas Schwab
2007-11-12 7:39 ` Vladimir Prus
2007-11-13 22:36 ` Stephen Berman
2007-11-13 23:24 ` Michael Snyder
2007-11-14 9:50 ` Stephen Berman
2007-11-14 12:00 ` Michael Snyder
2007-11-14 19:24 ` Stephen Berman
2007-11-15 1:00 ` Michael Snyder
2007-11-11 23:01 ` Stephen Berman
2007-11-12 5:15 ` Michael Snyder
2007-11-14 9:55 ` Stephen Berman
2007-11-14 12:00 ` Michael Snyder
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87hcjtllau.fsf@escher.local.home \
--to=stephen.berman@gmx.net \
--cc=gdb@sources.redhat.com \
/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.
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).