Debugging an L4 task

[Frank Mehnert]

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
-- 
## Dept. of Computer Science, Dresden University of Technology, Germany ##
## http://os.inf.tu-dresden.de/~fm3                                     ##
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://os.inf.tu-dresden.de/pipermail/l4-hackers/attachments/20050602/4ca05c93/attachment-0001.sig>