This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/15650] xemacs gdb cleanups.c:264: internal-error: restore_my_cleanups: Assertion '*pmy_chain == SENTINEL_CLEANUP' failed
- From: "palves at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Thu, 20 Jun 2013 08:37:03 +0000
- Subject: [Bug gdb/15650] xemacs gdb cleanups.c:264: internal-error: restore_my_cleanups: Assertion '*pmy_chain == SENTINEL_CLEANUP' failed
- Auto-submitted: auto-generated
- References: <bug-15650-4717 at http dot sourceware dot org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=15650
Pedro Alves <palves at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
CC| |palves at redhat dot com
--- Comment #9 from Pedro Alves <palves at redhat dot com> ---
> From cygwin terminal, I ran xemacs as a background process via "xemacs &"
> which gave me the PID 6040.
That's definitely not the PID you want. Also, "bt" after attach will not show
the thread we need (Windows injects a thread in the process to stop it; that's
where that DbgBreakPoint comes from.)
Run gdb in xemacs until you get the error. At the time it's asking you to
"Create a core file?...", look for the running _gdb_'s PID. It's GDB you want
to attach to, not xemacs. E.g., "ps -ef | grep gdb" in the cygwin shell may
work. Then do "gdb -p PID" -> "thread apply all bt".
--
You are receiving this mail because:
You are on the CC list for the bug.