Re: Palm Debugger on Tunsten/T

[Ben Combee]

Tracing has a bizare problem.  Given the sequence
    jsr   foo
    move.w #1, d0
    move.w #2, d1
    move.w #3.d2
When you are stopped in the debugger at the JSR, step over the JSR with F10,
it looks normal (new instruction is the "move.w #1...".  Do another step
with
F10 and the debugger steps to the "move.w #3...".  It does not stop and show
the
"move.w #2....", although register d1 will now contain 2 (the skipped
instruction
is executed, but not displayed by the debugger.  The F10 over the jsr has
left
some residual status in the debugger that causes the next step to execute 2
instructions.

Rob, we just saw this behavior earlier this week in final testing of the new debugger in CodeWarrior for Palm OS V9. This occurs with both the Palm Tungsten T and the Sony NX70V, so I would theorize that it is a bug with the ARM-native PACE debugger nub. This is not a Palm Debugger problem, but is a problem with the software on the device that is emulating the 68K processor.

The debugger in CodeWarrior for Palm OS V9 has a fix for this problem; it will ship out to customers who have preordered the product starting next Friday, December 20th. We've reported details of the device bug as well as our workaround for the problem to PalmSource.

ROM routine names are not displayed.  Most show as "ILLEGAL ADDRESS", or
just _TD xxx.  Obviously there are no routine names following the RTS
instructions
since the 68k is just a figment of our imagination...

Actually, the reality of the 68K processor doesn't affect Macsbug symbols... you either compile them into your binary or you don't. The debugger engine that runs on the Tungsten T is able to return symbol names when they are present.

--
Ben Combee <[EMAIL PROTECTED]>
CodeWarrior for Palm OS technical lead
Palm OS programming help @ www.palmoswerks.com


--
For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/