You may be right. I crashed and I couldn't get a backtrace. It did say I failed at a specific point in the code, though. Not the crash I wanted, but the crash I got. Backtrace didn't seem to work, though.
... intervals.c:1974: Emacs fatal error: assertion failed: charpos <= ZV && charpos >= BEGV This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. warning: BTMMHOOK 23.12.2011 12:23:13 Thread<2448> Hook DLL unloaded [Inferior 1 (process 6676) exited with code 03] (gdb) bt full No stack. (gdb) bt No stack. (gdb) therad apply all bt full Undefined command: "therad". Try "help". (gdb) thread apply all bt full (gdb) xbacktrace Undefined command: "xbacktrace". Try "help". (gdb) On Fri, Dec 23, 2011 at 10:49 AM, Matthew Fidler <matthew.fid...@gmail.com>wrote: > Joseph, > > I am using Windows XP. I am also using the mingw gdb program. I think > cygwin should work too. > > I downloaded from http://alpha.gnu.org/gnu/emacs/windows/ and I can see > that GDB loads the symbols: > > GNU gdb (GDB) 7.3.1 > Copyright (C) 2011 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 "mingw32". > For bug reporting instructions, please see: > <http://www.gnu.org/software/gdb/bugs/>... > *Reading symbols from > e:\emacsportable.app\app\emacs-24.0.92\bin\emacs-24.0.92.exe...done.* > Starting program: > e:\emacsportable.app\app\emacs-24.0.92\bin\emacs-24.0.92.exe - > -font "Inconsolata-16" -fg #e1e1e0 -bg #2d3743 -g 85x30+0+0 > [New Thread 9316.0x1f10] > [New Thread 9316.0x22a4] > warning: BTMMHOOK 23.12.2011 10:34:43 Thread<22A4> Hook DLL loaded > > [New Thread 9316.0x1acc] > [New Thread 9316.0xca8] > [New Thread 9316.0x1b70] > [New Thread 9316.0x2520] > [New Thread 9316.0x1478] > warning: frame 038EF800 (___EmacsPortableDaemon_24.0.92___) obscured > > [New Thread 9316.0x25f4] > [New Thread 9316.0x1f08] > [New Thread 9316.0x20d4] > [New Thread 9316.0x27dc] > [New Thread 9316.0x2338] > [New Thread 9316.0x20b4] > [New Thread 9316.0x1738] > [New Thread 9316.0x25fc] > [New Thread 9316.0x1b1c] > [New Thread 9316.0x22f4] > [New Thread 9316.0x2778] > [New Thread 9316.0x2568] > [New Thread 9316.0x1be8] > [New Thread 9316.0x248c] > [New Thread 9316.0x269c] > [New Thread 9316.0x24c4] > [New Thread 9316.0xcac] > [New Thread 9316.0x2338] > [New Thread 9316.0x1f74] > [New Thread 9316.0x257c] > [New Thread 9316.0x27ac] > [New Thread 9316.0x229c] > [New Thread 9316.0x27a8] > [New Thread 9316.0x24e8] > [New Thread 9316.0xdcc] > [New Thread 9316.0x21f0] > [New Thread 9316.0x1f4c] > [New Thread 9316.0x26c8] > [New Thread 9316.0x21a8] > [New Thread 9316.0x26fc] > [New Thread 9316.0x2410] > [New Thread 9316.0x26a0] > [New Thread 9316.0x1e50] > warning: reader_thread.SetEvent failed with 6 for fd 5 > > [New Thread 9316.0x2558] > [New Thread 9316.0x24a0] > warning: frame 038EF800 (___EmacsPortableDaemon_24.0.92___) reexposed by > WM_PAIN > T > > warning: obscured frame 038EF800 (___EmacsPortableDaemon_24.0.92___) found > to be > visible > > [New Thread 9316.0x1844] > [New Thread 9316.0x1ebc] > warning: frame 038EF800 (___EmacsPortableDaemon_24.0.92___) obscured > > warning: frame 038EF800 (___EmacsPortableDaemon_24.0.92___) obscured > > warning: obscured frame 038EF800 (___EmacsPortableDaemon_24.0.92___) found > to be > visible > > warning: frame 038EF800 (___EmacsPortableDaemon_24.0.92___) obscured > > warning: frame 038EF800 (___EmacsPortableDaemon_24.0.92___) obscured > > warning: frame 038EF800 (___EmacsPortableDaemon_24.0.92___) reexposed by > WM_PAIN > T > > warning: obscured frame 038EF800 (___EmacsPortableDaemon_24.0.92___) found > to be > visible > > > > > On Fri, Dec 23, 2011 at 10:40 AM, Joseph Jones > <darkdescend...@gmail.com>wrote: > >> Eli, >> >> I have tried these steps multiple times and have about given up ever >> getting something usable from this. Both Emacs23 and Emacs24 (latest drop) >> crash like this for me and I in no way can get you symbols. I was hoping >> that maybe it was just me... >> >> I will note that Emacs 23.3 crashes far less often then the Emacs 24 >> drops do. >> >> I am wondering if it has something to do with IDO or SMEX in that most of >> the crashes I get are when doing filename or other completion in the mode >> line. I haven't been able to really narrow it down as of yet since I >> haven't had the time to do it at work (where I get the crash). >> >> Matthew, >> >> What version of Windows are you using? I use Windows Server 2003 and see >> the crashes there but I never saw them on Windows 7. >> >> >> -Joe >> >> On Dec 23, 2011, at 7:14 AM, Eli Zaretskii wrote: >> >> >> Date: Fri, 23 Dec 2011 09:02:24 -0600 >> >> From: Matthew Fidler <matthew.fid...@gmail.com> >> >> >> >> I downloaded the version that is supposed to have debugging symbols >> and gtb >> >> still says "no debugging symbols found." >> > >> > Probably because you are looking at a backtrace of the wrong thread. >> > >> > "info threads" will show you what other threads exist. >> > >> > "thread apply all bt" will show a backtrace of each thread. >> > >> >> >
