Back-tracing in MIPS-based Linux Systems

More documents

Recommendations

Info

Back-tracing from The Signal Context 16 Great Company Great People
Signal Handler Context � backtrace_mips32 can’t handle stack-frames from signal contexts � In the signal handler context: � $ra points to the code block (by kernel) in the stack � backtrace_mips32 can’t handle this non-function code block � To back-trace from signal contexts: � Skip the kernel-inserted code/data block by referencing the signal context structure (ucontext_t) given to the signal handler � Handle the possible leaf function at the top of the call-stack ● No saved return address ● No stack-frame 17 Great Company Great People
Page 1 and 2: Back-tracing in MIPS-based Linux Sy
Page 3 and 4: Backgrounds 3 Great Company Great P
Page 5 and 6: Back-tracing � In many cases, it
Page 7 and 8: MIPS Stack-frame Structure 7 Great
Page 9 and 10: Real-world MIPS Stack-frame Structu
Page 11 and 12: Binary Code Scanning � The stack-
Page 13 and 14: Back-tracing Procedure � Initiali
Page 15: acktrace_mips32 Function � Workin
Page 19 and 20: sigbacktrace_mips32 Function � Wo
Page 21 and 22: Sample Applications 21 Great Compan
Page 23 and 24: Sample Application #1 � Simple ap
Page 25 and 26: Outputs from The Application (Strip
Page 27 and 28: Sample Application #2 � Same with
Page 29 and 30: Accompanied to objdump Utility �
Page 31 and 32: Summary � Back-tracing in the MIP
Page 33 and 34: Appendix: Crash Report System Appli
Page 35 and 36: Block Diagram Transmit Store log Ex

Back-tracing in MIPS-based Linux Systems

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?