PASD Limitation ?
pjv
Posts: 1,903
Hi All;
I'm working with the PASD debugger, and having some success. However, there is something I don't get quite right.
My Spin application simply launches one assembly cog, and that one launches another assembly cog. I intend, at least at first, to debug my first assembly cog, but the debugger points itself at the instruction in location C of the second cog, which does not (yet) have the 12 long lead-in kernel. When I remove the second cog, it points to the instruction at location C of the first cog, as it should.
How do I convince it to debug the first, and not the second?
And later how will I convince it to debug the second (third and forth) and not the first (or second/third)?
All my (very basic) assembly code is in a single DAT block, with leading org's and trailing longs applied·with each cog.
Help please??
Cheers,
Peter (pjv)
·
I'm working with the PASD debugger, and having some success. However, there is something I don't get quite right.
My Spin application simply launches one assembly cog, and that one launches another assembly cog. I intend, at least at first, to debug my first assembly cog, but the debugger points itself at the instruction in location C of the second cog, which does not (yet) have the 12 long lead-in kernel. When I remove the second cog, it points to the instruction at location C of the first cog, as it should.
How do I convince it to debug the first, and not the second?
And later how will I convince it to debug the second (third and forth) and not the first (or second/third)?
All my (very basic) assembly code is in a single DAT block, with leading org's and trailing longs applied·with each cog.
Help please??
Cheers,
Peter (pjv)
·
Comments
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
--Steve
Propeller Tools