Do I need the Lucid Wigit Library files for proper debugging? Matt.
On Sun, Jan 1, 2012 at 12:12 AM, Matthew Fidler <matthew.fid...@gmail.com>wrote: > Not yet. I haven't used my computer at all this week. > > Matt > > On Dec 31, 2011, at 8:41 PM, Joseph Jones <darkdescend...@gmail.com> > wrote: > > > Matthew, > > > > Any luck? > > > > On Dec 23, 2011, at 4:42 PM, Matthew Fidler wrote: > > > >> Ah, > >> > >> I will run gdb with the options file. > >> > >> Matt > >> > >> On Dec 23, 2011, at 5:03 PM, Eli Zaretskii <e...@gnu.org> wrote: > >> > >>>> Date: Fri, 23 Dec 2011 12:42:13 -0600 > >>>> From: Matthew Fidler <matthew.fid...@gmail.com> > >>>> > >>>> ... > >>>> intervals.c:1974: Emacs fatal error: assertion failed: charpos <= ZV > && > >>>> charpos > >>>>> = BEGV > >>> > >>> Where's the rest of this? This is something I could work with, but I > >>> need the rest of this backtrace. > >>> > >>>> [Inferior 1 (process 6676) exited with code 03] > >>>> (gdb) bt full > >>>> No stack. > >>> > >>> Too late: you let Emacs exit, and there's no way to debug it now. Do > >>> NOT let Emacs continue when it hits an abort or fatal signal, get the > >>> backtrace right there and then > >>> > >>>> (gdb) xbacktrace > >>>> Undefined command: "xbacktrace". Try "help". > >>> > >>> You need to download the .gdbinit file, which defines xbacktrace (and > >>> many other commands useful for debugging Emacs). Get .gdbinit from > >>> here: > >>> > >>> http://bzr.savannah.gnu.org/lh/emacs/trunk/annotate/head:/src/.gdbinit > >>> > >>> Then either start GDB from the directory where you put this file, or > >>> type at GDB's prompt: > >>> > >>> (gdb) source /path/to/.gdbinit > > >
