Re: Multiprocessor crash.

Hi,
  we are having a crash that is quite hard to catch at a client. Looking
at our log file, I can see that there is a context switch done at a
strange place. We have the following output:

09:43:17.718 {14412} filter: not adding key 738
09:43:17.718 {14412} filter: not adding key 737
09:44:25.328 {10804} ~~~ updating count thread ~~~
09:44:25.968 {14412} update top list item

We have these two message map entries:
ON_MESSAGE( UPDATE_WORKLIST, OnUpdateWorklistGui )
ON_MESSAGE( UPDATE_TOP_LIST_ITEM, OnUpdateTopListItem )

In this sample the GUI thread is 14412. The first two lines are written
while handling OnUpdateWorklistGui. It switches to 10804 (a worker thread)
before completly handling the OnUpdateWorklistGui message.

When the context returns to 14412, I would think that it would finish
handling the OnUpdateWorklistGui message, but instead of that it picks the
other one that was waiting in the message queue, i.e. OnUpdateTopListItem.

I know that nothing in the OnUpdateWorklistGui is triggering the
OnUpdateTopListItem message. The OnUpdateTopListItem is triggered by
another worker thread.

It feels to me like the context switch is messed up somehow.

Is this a behavior on dual core workstations running Windows XP SP2?
Can I force my application to always finish the processing of one message
before jumping to another message in the same GUI thread?
Or can I force my application to only use one processor (that is if the
problem could be dual core processor related)?

Thank you very much for your help,
Pete