Robert Shearman wrote:
Yep, example of what not to do in concurrent programming. You should
Tell me about it - I do hard realtime for a living.
One of the locks is the Win6 lock, another does not seem to have a name
(shown as "?" when things go bad). I wonder if, under Real Windows, the
Win
David D. Hagood wrote:
Robert Shearman wrote:
David D. Hagood wrote:
Unless the installer is using TryEnterCriticalSection, I would expect
CPU utilisation to be 0% when deadlocking.
Yes, *once the deadlock occurs* the CPU drops to 0%. The issue (I
think) is more along the lines of t
Robert Shearman wrote:
David D. Hagood wrote:
Unless the installer is using TryEnterCriticalSection, I would expect
CPU utilisation to be 0% when deadlocking.
Yes, *once the deadlock occurs* the CPU drops to 0%. The issue (I think)
is more along the lines of this:
On fast CPU:
thread
David D. Hagood wrote:
I may have a repeatable case of an error in locking critical sections,
so I'd like some pointers as to how to debug this.
The case occurs with the installer for Delorme Street Atlas 5 - on my
2GHz Athlon desktop it runs without a hitch, but on my oold slow
laptop (
I may have a repeatable case of an error in locking critical sections,
so I'd like some pointers as to how to debug this.
The case occurs with the installer for Delorme Street Atlas 5 - on my
2GHz Athlon desktop it runs without a hitch, but on my oold slow
laptop (how old is it? It's s
