As directed by the IOC output(!):
Asyn 4-8, streamDevice 2-2, EPICS 188.8.131.52, vxWorks 5.5.1 on MVME5500
(garbage elided): A call to "assert
in ../../asyn/asynDriver/asynManager.c at 2151
Current time THU JUN 21 2007 14:09:51.144096000.
EPICS Release EPICS R184.108.40.206 $R3-14-8-2$ $2006/01/06 15:55:13$.
Please E-mail this message and the output from "tt (0x1ed441a0)"
The backtrace is:
#0 0x22bbf4 in taskSuspend ()
#1 0x1e8ccebc in epicsThreadSuspendSelf ()
#2 0x1e8cb908 in epicsAssert ()
#3 0x1e754ac8 in interruptEnd (pasynPvt=0x1ed40fe0)
#4 0x1e75924c in callInterruptUsers (pasynUser=0x1eafb798,
data=0x1ed40b20 (as before),
#5 0x1e75959c in readRaw (drvPvt=0x1ed411d0,
#6 0x1e75ddd0 in readIt (ppvt=0x1ed40f70,
#7 0x1e745d54 in AsynDriverInterface::readHandler ()
#8 0x1e747dc4 in handleRequest ()
#9 0x1e74ea8c in portThread (pport=0x1ed446b0) at
#10 0x1e8cd600 in createFunction ()
#11 0x231ff8 in vxTaskEntry ()
Clearly something is getting overwritten, and at the point of the
assertion failure, (struct interruptBase *)pasynPvt->pport = 0x2c,
obviously bogus. In fact the pasynPvt passed in to interruptEnd is
I know that the cause may be entirely unrelated to this trace, but if
anyone can shed light on it, I'd be grateful. I have a debugger
attached, and am slowly working through...
The only anomaly I can see so far is that while readIt() has
maxchars=63, readRaw has maxchars=600, and so 600 bytes get transferred
and passed back to the interrupt user.
Peter Denison, Senior Software Engineer
Diamond Light Source Ltd.
Tel: +44 1235 778511
(apologies for the lines below. 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
- Re: Asyn assertion failure (long) Dirk Zimoch
- Navigate by Date:
Re: iocLogServer to Oracle or other rdb? Greg Lawson
Asyn and a 3rd party API? Bertrand H.J. Biritz
- Navigate by Thread:
RE: ioc shutdown hook? Denison, PN (Peter)
Re: Asyn assertion failure (long) Dirk Zimoch