This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: No useful backtrace in core dump.


On Thu, Apr 22, 2010 at 05:02:10PM +0800, äåæ wrote:
> http://sources.redhat.com/ml/gdb/2008-08/msg00123.html
> From above thread:
> Indeed, changing abort() to invalid memory reference makes backtrace work.
> foo (int a, int b)
> {
> int c=40;
> abort(); <--- IIUC, change to invalid memory reference
> return a+b;
> }

This is basically refraining from using abort(), which you said could be
difficult for you to modify, especially since you don't know yet who
calls it.

As the first step, I'd run the app under gdb / gdbserver to find out the
caller.

With kind regards,
-- 
Baurzhan Ismagulov
http://www.kz-easy.com/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]