This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug gdb/15650] xemacs gdb cleanups.c:264: internal-error: restore_my_cleanups: Assertion '*pmy_chain == SENTINEL_CLEANUP' failed


http://sourceware.org/bugzilla/show_bug.cgi?id=15650

--- Comment #10 from edderic at gmail dot com ---
(In reply to Pedro Alves from comment #9)
> > 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".

First of all, thanks for all the help, Folks!

So I called Xemacs from Cygwin Terminal and ran gdb in Xemacs.

Then I did the following...



eu6pq@L1-JPS-228-T ~
$ ps -ef | grep gdb
   eu6pq    1932    4904 pty1     13:39:48 /usr/bin/gdb

eu6pq@L1-JPS-228-T ~
$ gdb -p 1932
GNU gdb (GDB) 7.6.50.20130508-cvs (cygwin-special)
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-cygwin".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Attaching to process 4164
[New Thread 4164.0x1304]
[New Thread 4164.0x158]
[New Thread 4164.0xab4]
Reading symbols from /usr/bin/gdb.exe...(no debugging symbols found)...done.
(gdb) thread apply all bt

Thread 3 (Thread 4164.0xab4):
#0  0x779a000d in ntdll!DbgBreakPoint () from
/cygdrive/c/Windows/SysWOW64/ntdll.dll
#1  0x77a2f896 in ntdll!DbgUiRemoteBreakin () from
/cygdrive/c/Windows/SysWOW64/ntdll.dll
#2  0x70e8e12f in ?? ()
#3  0x00000000 in ?? ()

Thread 2 (Thread 4164.0x158):
#0  0x779af8e5 in ntdll!ZwReadFile () from
/cygdrive/c/Windows/SysWOW64/ntdll.dll
#1  0x779af8e5 in ntdll!ZwReadFile () from
/cygdrive/c/Windows/SysWOW64/ntdll.dll
#2  0x76cbdd54 in ReadFile () from /cygdrive/c/Windows/syswow64/KERNELBASE.dll
#3  0x00000098 in ?? ()
#4  0x00000000 in ?? ()

Thread 1 (Thread 4164.0x1304):
#0  0x779b013d in ntdll!ZwWaitForMultipleObjects () from
/cygdrive/c/Windows/SysWOW64/ntdll.dll
#1  0x779b013d in ntdll!ZwWaitForMultipleObjects () from
/cygdrive/c/Windows/SysWOW64/ntdll.dll
#2  0x76cc15e9 in WaitForMultipleObjectsEx () from
/cygdrive/c/Windows/syswow64/KERNELBASE.dll
#3  0x00000002 in ?? ()
#4  0x014ea418 in ?? ()
#5  0x75d11a2c in WaitForMultipleObjectsEx () from
/cygdrive/c/Windows/syswow64/kernel32.dll
#6  0x75d14220 in WaitForMultipleObjects () from
/cygdrive/c/Windows/syswow64/kernel32.dll
#7  0x61005ff0 in cygwait(void*, _LARGE_INTEGER*, unsigned int) () from
/usr/bin/cygwin1.dll
#8  0xffffffff in ?? ()
(gdb)

-- 
You are receiving this mail because:
You are on the CC list for the bug.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]