Re: mutt 1.5.19: Segmentation fault
On Tuesday, 06 January 2009 at 22:32, Tobias Mummert wrote:
> * Brendan Cully [2009-01-06 22:14 CET]:
>
> > > > A backtrace would be great.
> > >
> > > Mutt hasn't produced a core file.
> > >
> > > What can I do now?
> >
> > Both cases are covered on that page. I've emboldened things a bit to
> > make it easier to read.
>
> Great, thank you very much, Brendan!
>
> Here is my back trace:
...
> (no debugging symbols found)
>
> warning: Can't read pathname for load map: Input/output error.
...
> Core was generated by `/root/tmp/mutt1519 -d5'.
> Program terminated with signal 11, Segmentation fault.
> [New process 13740]
> #0 0x0806eb0b in ?? ()
> (gdb) backtrace
> #0 0x0806eb0b in ?? ()
> #1 0x08204988 in ?? ()
> #2 0x080d9a35 in ?? ()
> #3 0x00000000 in ?? ()
Hmm, that didn't go very well. Can you try the other strategy, running
mutt inside of gdb? Also, -d2 is plenty.