public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "edderic at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/15650] xemacs gdb cleanups.c:264: internal-error: restore_my_cleanups: Assertion '*pmy_chain == SENTINEL_CLEANUP' failed
Date: Wed, 19 Jun 2013 19:36:00 -0000 [thread overview]
Message-ID: <bug-15650-4717-PhyEsKPwJY@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15650-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=15650
--- Comment #4 from edderic at gmail dot com ---
(In reply to Tom Tromey from comment #3)
> What I would do is wait for the crash, then attach another gdb to the
> crashing gdb using the "attach" command. Then "bt".
> Alternatively a core dump would work just as well.
gdb in xemacs after the error asked me if I wanted to create a core file:
"Create a core file of GDB? (y or n)"
I typed "y" and pressed "Enter"
And then it said Inferior GDB exited abnormally with code 1.
I then found gdb.exe.stackdump and here's what it said:
Stack trace:
Frame Function Args
That's it...
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-06-19 19:36 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 15:16 [Bug gdb/15650] New: " edderic at gmail dot com
2013-06-19 15:19 ` [Bug gdb/15650] " edderic at gmail dot com
2013-06-19 17:28 ` tromey at redhat dot com
2013-06-19 17:43 ` edderic at gmail dot com
2013-06-19 18:16 ` tromey at redhat dot com
2013-06-19 18:21 ` jan.kratochvil at redhat dot com
2013-06-19 19:36 ` edderic at gmail dot com [this message]
2013-06-19 19:41 ` jan.kratochvil at redhat dot com
2013-06-19 20:23 ` edderic at gmail dot com
2013-06-19 20:32 ` edderic at gmail dot com
2013-06-19 20:49 ` jan.kratochvil at redhat dot com
2013-06-20 8:37 ` palves at redhat dot com
2013-06-20 17:52 ` edderic at gmail dot com
2013-06-20 18:03 ` palves at redhat dot com
2013-06-20 18:32 ` edderic at gmail dot com
2013-06-20 19:01 ` tromey at redhat dot com
2013-06-20 19:15 ` edderic at gmail dot com
2013-06-20 20:17 ` tromey at redhat dot com
2013-06-21 10:28 ` palves at redhat dot com
2013-06-21 17:26 ` edderic at gmail dot com
2013-06-21 19:31 ` tromey at redhat dot com
2013-06-21 19:47 ` edderic at gmail dot com
2013-06-23 16:52 ` sergiodj at redhat dot com
2013-06-24 18:13 ` edderic at gmail dot com
2013-06-24 19:44 ` edderic at gmail dot com
2013-06-24 19:47 ` edderic at gmail dot com
2013-06-24 19:47 ` edderic at gmail dot com
2013-07-24 22:33 ` kris at asc dot uk.com
2013-07-29 18:30 ` jan.kratochvil at redhat dot com
2013-08-02 7:48 ` kris at asc dot uk.com
2013-08-02 7:52 ` jan.kratochvil at redhat dot com
2013-08-02 8:38 ` kris at asc dot uk.com
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=bug-15650-4717-PhyEsKPwJY@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.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.
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).