Multithreading Oddness

[Joel Holdsworth]

Bizzare! Replacing the CCriticalSection with a CMutex made the problem go away !?! Joel Holdsworth

[peterchen]

That's weird. The main differences between critical sections and mutices is (a) mutices work cross-process, and (b) have a different timing. I suspect you still have a bug lurking in your code, that is hidden / uncovered depending on timing.

---

Pandoras Gift #44: Hope. The one that keeps you on suffering.
aber.. "Wie gesagt, der Scheiss is' Therapie"
boost your code || Fold With Us! || sighist | doxygen

[Joel Holdsworth]

Agreed, however I time is not a luxury I have right now! I am seriously short of time. Joel Holdsworth

[Laffis]

what do u mean by sleep. You called Sleep()? That freezes the thread! You should never use that func if you want the thread to be able to process something else at the same time!

[kerrywes]

so let me understand this, you call each worker from your main process, then sleep in main? this s what you should do, but i suspect this is not the case... a 'good' model: while(1) { // call your threadproc sleep(L5); // watever else } dont use sleep in threadproc, this suspends execution

[Joel Holdsworth]

No No! The worker does the sleeping! The main process never stops - it just runs the message pump! Joel Holdsworth

[Laffis]

Main process and the worker thread are both threads. You call Sleep in the w-thread, it will be suspended there sleepting, and not able to receive and new message. I assume your w-thread does task when told, i.e. when getting a message to trigger execution of certain functions. If your w-thread cannot receive message, no wonder your func does not get called, let alone hit your critical section.

[Steen Krogsgaard]

Well, sleep() only sleeps for the time specified. As I understand the OP he has something like // worker thread ... sleep(sometime); myCriticalSection.Lock() // this is where the worker hangs here the sleep() call will only block the worker thread for sometime milliseconds and are thus not in itself a problem. Cheers Steen. "To claim that computer games influence children is ridiculous. If Pacman had influenced children born in the 80'ies we would see a lot of youngsters running around in dark rooms eating pills while listening to monotonous music"

[kerrywes]

thats the problem then, Sleep() suspends threads and may mess with the crit sect timing, movr Sleep() to main() and that should fix your issue. why do you sleep in worker threads anyway? do u see the oxymoron? :)

[cmk]

If, while debugging the code, the app hangs hit break (not stop). By looking at the threads you can see what each is executing. Put the CCriticalSection in the variable watch list and open it up. Inside you should find the root critical section object. One of the members of this structure is the owning thread. Look in the debugger thread list and see what that thread is doing. ...cmk Save the whales - collect the whole set