Hi Chris,
I'm not sure if this may help, but depending on gcc version, it has some
backtrace functions you can use. Take a look at this, maybe it can help?
http://stackoverflow.com/questions/77005/how-to-generate-a-stacktrace-when-my-gcc-c-app-crashes
Regards, Stuart
On 14/09/15 14:16, Chris Westervelt wrote:
Hey I don't know if anyone out there in LTIB land has successfully
done this or not but With all of the approaches I have tried off the
internet to get a stack backtrace of my crashed application code on an
LPC3250 CPU and Kernel 2.6.34, nothing has worked. I have tried also
using 'catchsegv' but the output does not make any sense. My code has
deliberate SEGV errors to induce the dump code to work but the output
is nonsensical. I find it interesting that when running debug with
the exact same code (Debug build) the GDB utility does a fine job of
showing the stack back trace just the way I would like to see it
almost but I have no idea how it does that. Also a common problem
with ARM is the back trace count only accounts for 1 entry which is
the return from error interrupt (useless duh). Any suggestions I will
repay with kindness when I can answer one of your questions.
*Chris Westervelt*
*Senior Product Development Engineer*
*Advantor Systems.
12612 Challenger Pkwy
Suite 300
Orlando, FL
32826*
*http://www.advantor.com <http://www.advantor.com/>
Office: (407) 926-6983*
*Mobile: (407) 595-7023
Fax: (407) 857-1635*
*Notice of Confidentiality:*
This e-mail communication and the attachments hereto, if any, are
intended solely for the information and use of the addressee(s)
identified above and may contain information which is legally
privileged and/or otherwise confidential. If a recipient of this
e-mail communication is not an addressee (or an authorized
representative of an addressee), such recipient is hereby advised that
any review, disclosure, reproduction, re-transmission or other
dissemination or use of this e-mail communication (or any information
contained herein) is strictly prohibited. If you are not an addressee
and have received this e-mail communication in error, please advise
the sender of that circumstance either by reply e-mail or by telephone
at (800) 238-2686, immediately delete this e-mail communication from
any computer and destroy all physical copies of same.**
_______________________________________________
LTIB home page: http://ltib.org
Ltib mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/ltib
_______________________________________________
LTIB home page: http://ltib.org
Ltib mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/ltib
