Re: how do i get a backtrace? (was Re: mutt crash and backtrace)
* On 2005.02.28, in <20050301035847.GA27356@xxxxxxxxxxxxxxx>,
* "Charlie Allom" <charlie@xxxxxxxxxxxxxx> wrote:
>
> I have --enabled-debug and can replicate a bug with headercache i think.
>
> Now i'd like to find a proper error rather than:
>
> [Bus Error]
First, you might need to set the resource limit for core dump sizes.
This is often set to 0 by default to prevent core dumps from taking up
lots of disk space. How to do this depends on your shell -- see man
pages for ulimit (sh/ksh/zsh/bash) or limit and unlimit (csh/tcsh). Set
it to unlimited.
Once that's done, repeat the bug. It should generate a core file.
Usually that's in the current directory and named "core", but this can
vary from one OS to another.
Once you know where the core file is, use gdb to get a backtrace:
gdb /path/to/mutt /path/to/core/file
[lots of output from gdb]
gdb> backtrace
or
gdb> bt
--
-D. dgc@xxxxxxxxxxxx NSIT::ENSS
"So now, less than five years later, you can go up on a steep hill...
and with the right kind of eyes you can almost see the high-water
mark -- the place where the wave finally broke and rolled back." -HST