Andy,
Not meaning to rub salt in a healing wound, but what was the cause (or
better yet resolution) of the extra thread problem? I'm asking because I'm
having some pretty serious problems with code that works on 5.0 but turns to
mush under 5.1. I have some largely self imposed time pressure on me, so at
this point I plan to mine my 5.1 image for changes to my 5.0 image.
Sadly, the show stopper turned out to be the last thing I expected to give
me trouble; that and pragmatic issues cause it to become the last thing that
I tested. It involves multiple threads that read and write through a serial
port, conversing with a device that is not known for forgiveness. As an
example, the thread that reads isn't getting anything, but that could
because the device didn't get the request that had to go out first (though
tracing suggest that it should have), that the request was mangled in some
way, that the device didn't respond, or that the data isn't being read. I
can sort most of that out, but it will take time. Obviously, my code could
also have changed because of changes in the image, compiler optimizations,
or because I simply didn't load all of it.
Any suggestions?
Have a good one,
Bill
--
Wilhelm K. Schwab, Ph.D.
[hidden email]
Locked
