On Mon, Aug 9, 2010 at 13:03, Gibson, David wrote: > I was hoping to debug the non-static build of the test to see what it does > but the exceptions handling functions are not debugable (as presumably > they’re part of a shared library/kernel).
they should be ... but i'm not terribly familiar with how C++ exceptions are actually implemented. we arent using the old sjlj methods right ? we're using modern RT signals ? > So to achieve this what I think I > need to do is have the application running under gdbserver on the board, > then on the host, start up kgdb and debug the kernel while running the > application on the board over the exceptions handling code. if exceptions are being thrown via RT signals, then having a second gdb session connected to the kernel would be useful. you could use kgdb, but you could also just use an ICE-100B or gnICE and connect with jtag/gdbproxy. that way you dont have to worry about building a different kernel (one with kgdb) instead of the one actually crashing ... -mike _______________________________________________ Toolchain-devel mailing list [email protected] https://blackfin.uclinux.org/mailman/listinfo/toolchain-devel
