[OpenSER-Devel] debugging core files

Norman Brandinger norm at goes.com
Thu Aug 30 02:49:23 CEST 2007




First start gdb as follows:

gdb openser core.22311

(you might need to
use fully qualifies pathnames ie: /usr/local/sbin/openser)

Once gdb started, type bt on
the command line (bt = backtrace).

The resulting output should give you more
information about the state of processing at the time of the core.

Regards.
Norm


> When I attempt to open a core it usually says this: 
> 
> (gdb) core core.22311 
> Core was generated by `/usr/local/sbin/openser'. 
> Core file contained no thread-specific data 
> 
> I compile this these
flags: 
> CFLAGS+=-O1 -ggdb3 -fno-omit-frame-pointer 
> 
> Anyone know of
any debugging tips for openser core files? 
> I would like to see the backtrace etc.. 
> 
> 
> -will 
> _______________________________________________ 
> Devel mailing list 
> Devel at openser.org 
>
http://openser.org/cgi-bin/mailman/listinfo/devel 
> 


Global Online
(GOES) 
271 Main St., Suite C 
Hackettstown, NJ 07840-2032 
(908) 813-0600 x8105
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://openser.org/pipermail/devel/attachments/20070829/94134351/attachment.htm


More information about the Devel mailing list