[Cbe-oss-dev] How is a debugger supposed to find the SPU's PC value in a CBE core file?
Arnd Bergmann
arnd at arndb.de
Mon Jul 16 08:53:44 EST 2007
On Sunday 15 July 2007, Benjamin Herrenschmidt wrote:
> > If you do not know which piece of (PPE) code will call that
> > interface,
> > and what PC parameter it will pass, you fundamentally cannot know
> > where the context will continue.
>
> Would it be useful to provide a mechanism for a debugger to set a "break
> on entry" flag on a context, causing either libspe or the kernel to
> trigger a breakpoint stop on the next attempt at running anything in
> that context, regardless of the PC value ?
I'd guess that the debugger can implement that without libspe2
or kernel support, simply by setting a breakpoint on the
spu_run syscall instruction in libspe2 and ignoring the
breakpoint if its run on a context that you are not tracing.
Arnd <><
More information about the cbe-oss-dev
mailing list