> I couldn't let the MemSemaphoreResxxx thing go... I twiddled with my
> simple tool and wound up tracing into the calls while the system was up
> and running. Along the way, I came across what seems like a bug in the
> 3.3 Roms, but I might be missing something...
>
> The first few lines of the trap appear to be:
>
> move.l d0,-(a7) ; save it
> move.w #0x2c, d0 ; the exception vector address that got us here
> bra <common> ; jump to a common exception handler
The first few lines of *what* trap? The code you're displaying is the code that
gets executed when an unexpected exception occurs.
> trap #F: SysFatalAlert ; ???? Won't this recurse until the stack explodes if
> ; trap #F got us here in the first place?
> <reset>:
> trap #F: SysReset ; ???? And this as well?
Trap #$F doesn't take you to that section of code. Trap #$F is handled by
another function. So there's no recursion.
> There also appear to be Trap #F codes which do
> not start with 0xA0xx. I had no idea these existed!
Well, there's 0xA1xx, 0xA2xx, 0xA3xx, etc. There's around 1000 Palm OS
functions after all. And there's also 0xA8xx for library functions. Or are you
talking about something else?
> One other dumb question - I understand why the MW debugger can't set
> breakpoints in ROM when debugging on a real device, but why doesn't it
> let you set breakpoints at arbitrary addresses when you are running with
> the POSE?
You might want to send this question to Metrowerks. There's nothing in Poser
that would prevent them from setting a ROM breakpoint.
-- Keith Rollin
-- Palm OS Emulator engineer
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
