U++ framework: U++ MT-multithreading and servers » Deadlock

Home » U++ Library support » U++ MT-multithreading and servers » Deadlock - what LeaveGMutexAll does?

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

Re: Deadlock - what LeaveGMutexAll does? [message #35067 is a reply to message #35037]

Sat, 07 January 2012 13:21

pete82
Messages: 3
Registered: November 2011

Junior Member

I solved it by queing all "Refresh" and all the other GUI calls to the main thread (which is quite uncomfortable).

Thank you for explanation, but do i understand correctly (also looking at the code), that the main thread is unlocking lock which it doesn't own? This looks really bad to me. The classic method to avoid deadlocks is to acquire them in some fixed order, but it fails then.
Basically, can this happen? (GM-GMutex,OM-other mutex,T-thread,MT-main thread)
T: GM->OM->GM unlocked, preempted
MT:waiting on GM->GM->waiting on OM
T: ->waiting on GM

Report message to a moderator

[Message index]

		Deadlock - what LeaveGMutexAll does? By: pete82 on Sun, 01 January 2012 12:35
		Re: Deadlock - what LeaveGMutexAll does? By: mirek on Sat, 07 January 2012 10:50
		Re: Deadlock - what LeaveGMutexAll does? By: pete82 on Sat, 07 January 2012 13:21
		Re: Deadlock - what LeaveGMutexAll does? By: mirek on Sat, 07 January 2012 15:04

Previous Topic:	Htmls / HtamlTag class and table generation
Next Topic:	What is the status of IPv6 support?

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sat Oct 03 13:16:35 GMT+2 2026

Total time taken to generate the page: 0.01262 seconds