> > 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>
You can do use the FREEZE and THAW swat commands to pause one thread
so another thread can be run. The help command should give you the
necessary syntax.
The problem you are having with threads not switching is because swat
has to take control of the target system to perform the stepping (or
whatever you are doing) in the current method. Allowing the system
to context switch another thread while you are halted in your method
would lead to a multitude of problems and confusion.
> 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.
Swat does try to set several breakpoints for its own use (if you do a
"brk list", you will see the first four breakpoints are set by swat).
Hope that helps.
-Ed-