Experimental Physics and
Industrial Control System

"Jeff Hill" <[email protected]> · Tue, 17 Jun 2008 09:31:37 -0600

Hello Mathew,

My best guess (subject to change of course :-) is that some tangential code
is corrupting the semaphore id used by a timer queue thread.

> epicsThread: Unexpected C++ exception "epicsEvent::invalidSemaphore()"

This is coming from the last chance exception handler in the epicsThread
class. It is not a message from the dreaded unexpected exception handler in
the CRTL (associated with violated exception specifications). I will fix the
message emitted by epicsThread so that this is clear in the future.

> > interrupt: Main interrupt with no cause
> > interrupt: Main interrupt with no cause

This output might be supporting evidence for the corruption theory.

Please try also the vxWorks shell "tt" command for the suspended thread.
That may, or may not, provide some useful information.

Jeff

> -----Original Message-----
> From: [email protected] [mailto:[email protected]]
> On Behalf Of Matthew Pearson
> Sent: Tuesday, June 17, 2008 6:52 AM
> To: Andrew Johnson
> Cc: [email protected]
> Subject: Re: unhandled exception in timerQueue
> 
> Update:
> 
> I've just seen the same again (after a reboot, and a couple of hours)...
> but the IOC shell is fine.
> 
> 0x1e0ab530 (timerQueue): Unhandled C++ exception resulted in call to
> terminate
> epicsThread: Unexpected C++ exception "epicsEvent::invalidSemaphore()"
> with type "Q210epicsEvent16invalidSemaphore" in thread "timerQueue" at
> TUE JUN 17 2008 11:50:26.620275542
> 
> I also see:
> 
> timerQueue 1ea3ad00     1e0ab530 148 SUSPEND      22bbf4 1e0ab090
> 3d0002     0
> 
> 
> Regards,
> Matthew
> 
> On Tue, 2008-06-17 at 13:46 +0100, Matthew Pearson wrote:
> > Hi Andrew / Tech-Talk,
> >
> > I've just seen the following printout in my vxWorks IOC shell (EPICS
> > 3.14.8.2):
> >
> > 0x1e0abd20 (timerQueue): Unhandled C++ exception resulted in call to
> > terminate
> > epicsThread: Unexpected C++ exception "epicsEvent::invalidSemaphore()"
> > with type "Q210epicsEvent16invalidSemaphore" in thread "timerQueue" at
> > FRI JUN 13 2008 16:51:01.488894248
> > 0x1e03e550 (timerQueue): Unhandled C++ exception resulted in call to
> > terminate
> > epicsThread: Unexpected C++ exception "epicsEvent::invalidSemaphore()"
> > with type "Q210epicsEvent16invalidSemaphore" in thread "timerQueue" at
> > FRI JUN 13 2008 16:56:38.279153464
> > interrupt: Main interrupt with no cause
> > interrupt: Main interrupt with no cause
> >
> >
> > It looks like an Q210epicsEvent16invalidSemaphore exception is thrown
> > from an epicsThread. But this seems to be unexpected, and unexpected()
> > is called, which seems to exit the IOC shell.
> >
> > Nick Rees suspects that this was discussed a while ago, and may have
> > been dealt with in a later version than 3.14.8.2. Any ideas?
> >
> > Regards,
> > Matthew Pearson
> >
> > DLS Controls
> >
> >
> >
> <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>

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System