[Asterisk-Users] Strange Crash

Steven Critchfield critch at basesys.com
Sun Jan 30 02:24:38 MST 2005


On Sun, 2005-01-30 at 12:46 +0330, Paradise Dove wrote:
> this is what i've typed to get the crash info:
> 
> gdb /usr/sbin/asterisk --core=/core.3673

Not sure if that is wrong, but I also see from the gdb man page that you
should be able to start it by

gdb /usr/sbin/asterisk /core.3673



> On Sun, 30 Jan 2005 03:11:24 -0600, Steven Critchfield
> <critch at basesys.com> wrote:
> > On Sun, 2005-01-30 at 12:31 +0330, Paradise Dove wrote:
> > > hi,
> > >
> > > just got an strange crash, and don't know what could cause this type of crashs
> > > - hardware failure
> > > - memory
> > > - cpu
> > > ....?
> > > i have 1xTE405P installed with 4xTA750. using fresh kernel 2.6.9 (no patch).
> > > * version is latest CVS HEAD.
> > >
> > > thanks
> > >
> > > Program terminated with signal 11, Segmentation fault.
> > > Cannot access memory at address 0xb80014bc
> > 
> > Seg faults can be faulty memory, overheated CPU, but usually it is an
> > error in programming.
> > 
> > > #0  0xb7fbbce4 in ?? ()
> > >
> > > (gdb) bt
> > > #0  0xb7fbbce4 in ?? ()
> > > #1  0x080d425d in _IO_stdin_used ()
> > > #2  0x00000000 in ?? ()
> > 
> > Next time provide the asterisk binary along with the core file to gdb so
> > you can get symbol names and line numbers.
> > 
-- 
Steven Critchfield <critch at basesys.com>




More information about the asterisk-users mailing list