On 6/2/05, Frank Mehnert fm3@os.inf.tu-dresden.de wrote:
Hi Derick,
On Thursday 02 June 2005 10:23, Derick Swanepoel wrote:
I am trying to debug an L4 task that double pagefaults before reaching the main function. How should one use the debugger to run a task so it can be debugged without having to break into the debugger later? The backtrace doesn't seem very useful because it looks like a stack overflow due to infinite recursion.
Why useless? What if it _is_ a recursion? Before continue to search, disassemble the binary and look which function is called from outs() (file log/lib/src/logliblinux.c). Start disassembling around 0x01604db0.
Frank
I didn't think the backtrace would be much use because the stack would've been corrupted due to the infinite recursion. But since I was linking to the wrong logging library it's not a problem anymore. Thanks for the debugging tip, though.
Derick