gdb breakpoint
Posted: Tue Jun 21, 2011 11:52 pm
Is there a reason why setting breakpoints in exeDSP wouldn't work? I'm trying to set a breakpoint on a call to printf. I can examine the memory, so I can see the call. It's printing a string that's unique as far as I can see in exeDSP, and I do see the string come out on exlink. I've tried this in various ways, but I can't set breakpoints that actually stop exeDSP.
I think I must be doing something very basic wrong, what could it be?
I think I must be doing something very basic wrong, what could it be?
. I'm still unaware of any (easy) solution for this problem. I guess there are some possible workarounds; e.g.: hijacking printf code in glibc (clever code injection of some kind will be required). That way, we can ensure any printf() call from exeDSP will additionally print SPID/TID of calling thread..
This is what I'm really after anyway. I plan to make a module that will let me insert calls to my own functions into exeDSP. This way I can printf registers, or whatever I want.
. Thank you. Debugging exeDSP is still not 100% perfect experience for me on B-series (I'm getting a lot of "Cannot get thread event message: debugger service failed" messages, and exeDSP is not always able to recover from stop conditions), but finally it's possible to utilize thread-aware gdb functionalities with this libthread_db.so version.