Re: [Ltib] libc backtrace and crash handlers

[Stuart Hughes]

Hi Kareem,

The libc in LTIB is from the toolchain.  Normally this will be eglibc,
which is effectively glibc.

What do you mean by a backtrace? do you mean a core file?  If so you may
need to change your ulimit settings, for example:

# ulimit -c unlimited

Regards, Stuart

Kareem Shehata wrote:
> Hello all,
> 
> I'm trying to implement a crash (a.k.a. application fault) handler for 
> several of my applications that run on an MX31.  I figured to use eCrash, 
> since it's pretty well what I would code if I were writing a crash handler.  
> It works great when compiled for my X86 linux box, and compiles and runs on 
> the MX31.  The problem is that it doesn't produce any backtrace information.  
> This is particularly strange, because gdb will give good backtrace info when 
> used, so the stack is there and all of the information.
> 
> First question: does the libc that ships with LTIB support backtrace()?
> 
> If so, why would it not produce decent backtraces?
> 
> If not, do you know of any way to get backtrace info in this environment?
> 
> Thanks!
> 
> Kareem
> 
> 
> --
> Kareem Shehata
> address@hidden
> Aeryon Labs Inc
> 519-489-6726 x254
> 
> 
> _______________________________________________
> LTIB home page: http://ltib.org
> 
> Ltib mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/ltib
>