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: "sergiodj at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Sun, 23 Jun 2013 16:52:25 +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
Sergio Durigan Junior <sergiodj at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sergiodj at redhat dot com
--- Comment #20 from Sergio Durigan Junior <sergiodj at redhat dot com> ---
(In reply to edderic from comment #19)
> Ok. How do I exactly do that? Do I need to find the source code for gdb and
> recompile it with -g and -O0? Sorry, I am not as skilled as any of you yet ;)
I am not experienced with Windows/Cygwin, but yes, he meant you need to get the
GDB source and compile it with -g and -O0. It would be interesting if you
could build using the latest CVS version. To get it, you can do a:
"cvs -d :pserver:anoncvs@sourceware.org:/cvs/src co gdb"
[Assuming CVS is installed on your system.] It will checkout the source code
inside a directory called "src/". Then, you can compile GDB:
$ cd src && mkdir mybuild && cd mybuild
$ ./configure CFLAGS='-g -O0' # check for missing deps here, install them
$ make
If everything works, you should have a GDB binary on the "gdb/" directory
(inside "mybuild/"). Then, you can try to reproduce the error with it, and get
a proper backtrace from it.
--
You are receiving this mail because:
You are on the CC list for the bug.