Re: how to debug (and fix) mutt?
On 2006-02-23, Bram Mertens <bram-mertens@xxxxxxxx> wrote:
> On 2006-02-22, Gary Johnson wrote:
> > On 2006-02-22, Bram Mertens <bram-mertens@xxxxxxxx> wrote:
> >
> > > Can I add some options to add more logging? Mutt is unusable like this
> > > at the moment.
> >
> > If you configured mutt with --enable-debug, mutt should dump a
> > debuggable core file when it segfaults. The stack backtrace from
> > the core file may provide more insight than the log file.
>
> According to the debian/rules file below the mutt source dir mutt is
> built with --enable-debug but no core file is produced. At least not
> where I'm looking for it, core files are dumped in the current dir,
> right?
Right.
> Can I start mutt from a debugger to get a stacktrace that way?
If you just want a stack backtrace, follow Toby's suggestions. You
can also get a stack backtrace by running mutt from gdb. The way I
prefer doing it, unless I'm debugging a startup problem, is to start
mutt in one xterm, then use ps to find mutt's process ID and attach
to it from a gdb running in a different xterm.
HTH,
Gary
--
Gary Johnson | Agilent Technologies
garyjohn@xxxxxxxxxxxxxxx | Wireless Division
http://www.spocom.com/users/gjohnson/mutt/ | Spokane, Washington, USA