> The behavior you're observing could be due to sending a message: When
> you send a message to an object that's run by a different thread as the
> currently-running thread, that message is placed on the queue, so may not
> be processed until after your current method is finished.
That seems to be the case: the message waits in the queue until I finish
current method in another, higher priority, thread.. and I went through
so much trouble making sure both threads could be doing their tasks at the
same time <sigh>
At least there won't surface any bugs later. Well, I ... <shrug>
> Are you debugging on the target PC, or on actual hardware? If the
> latter, then the warning means that Swat can't install a breakpoint
> because the code is in ROM. If the former, then it's hard to tell
I debug the real thing. So this is one of the limitations that were
mentioned in some document.. I've noticed a couple other ones eg. I
cannot "run" the application. I have to "spawn" and start indirectly.
I find that strange, but it might be due to the nature of the app.
Hmph.. code is in ROM? But all the code I swat is written by me and
"sent" to the device to replace the ROM version? I can set breakpoints
and they are found.. Does swat set some other breakpoints for itself,
when it switches threads? Something to remember where it stopped? That
would explain it == the other thread is system thread == in ROM.
Thanx again Paul, you've been a great help!
>Paul.
--jouni