EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: Deadlock on epicsEvent
From: "Denison, PN \(Peter\)" <[email protected]>
To: "Denison, PN \(Peter\)" <[email protected]>, "TechTalk EPICS" <[email protected]>
Date: Tue, 18 Sep 2007 11:20:17 +0100
> I'm trying to debug a deadlock on Linux under R3.14.8.2, on a 
> cut down IOC with only asyn, motor and autosave installed. 
> 
> What appears to be happening is that one thread is waiting on 
> an epicsEvent, whilst another thread is trying to signal that 
> event, but getting stuck on the event's internal lock. The 
> pthread man pages imply that this shouldn't happen.

There's nothing quite like asking in public to find out you've been
stupid, is there? Emerging from my brown-paper-bag, I've found the cause
of the problem. However, I think there is still room for improvement, as
the library code could have caught it, rather than deadlocking.

I was trying to signal an epicsEvent after having called
epicsEventDestroy() on it. Therefore the lock it was trying to acquire
was 0.

Is this a reason to put a cookie in the epicsEventOSD structure, to
check that it's a valid structure before using it? If the consensus is
that it's worth it, I'll get hacking.

-- 
Peter Denison, Senior Software Engineer, Diamond Light Source Ltd.
Tel: +44 1235 778511
(apologies in advance for the lines below. Some bits are a legal
requirement and I have no control over them)

<DIV><FONT size="1" color="gray">This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. 
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
</FONT></DIV> 


Replies:
RE: Deadlock on epicsEvent Jeff Hill
References:
Deadlock on epicsEvent Denison, PN (Peter)

Navigate by Date:
Prev: CMLOG error :( Heinrich du Toit
Next: CMLOG compile ... Heinrich du Toit
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Deadlock on epicsEvent Denison, PN (Peter)
Next: RE: Deadlock on epicsEvent Jeff Hill
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 10 Nov 2011 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·