On Sat, Jan 23, 1999 at 12:16:42PM +0100, Daniel González Gasull <[EMAIL PROTECTED]>
wrote:
[...]
> Thomas Roessler <[EMAIL PROTECTED]> wrote some time ago:
[...]
> > About the segmentation faults you are experiencing:
> > Could you please switch on core dumps on your
> > machines, and inspect the resulting core with gdb
> > and friends? A stack trace would be helpful in
> > particular.
>
> I've done it as the Mutt FAQ says:
>
> # mutt
> Segmentation fault
> # gdb /usr/local/bin/mutt core
[...]
> /root/core: No such file or directory.
> (gdb) bt
> No stack.
> (gdb) q
Make sure you can dump core ("unlimit coredumpsize" on most shells, I
think) and then make mutt dump core again. Make sure that there is a
file called core. Make sure that you are in the same directory as it.
Make sure the path to mutt you specify when you invoke gdb is the same
as the path to the mutt that dumped core. Then try running gdb on the
core file, as above, and you should get an actual stack trace when you
type "bt".
Send that to us, it will actually help (perhaps.) Another question:
are you running a weird version of libc by any chance? More information
will help most of all, but I have run across cases of mutt crashing
because it was linked against a linux libc with horribly buggy regexp
routines. So try doing "make distclean" and then rerunning configure
with the flag "--with-rx" and see if that helps, too.
-Daniel
--
Daniel Eisenbud
[EMAIL PROTECTED]
