Subject: |
[Bug 541330] Re: 'assert (size <= ntohs ( pMsg->m_postsize ))' failed in ..caserverio.c line 344 |
From: |
Andrew Johnson via Core-talk <[email protected]> |
To: |
[email protected] |
Date: |
Tue, 15 Oct 2019 14:54:37 -0000 |
** Changed in: epics-base
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of EPICS
Core Developers, which is subscribed to EPICS Base.
Matching subscriptions: epics-core-list-subscription
https://bugs.launchpad.net/bugs/541330
Title:
'assert (size <= ntohs ( pMsg->m_postsize ))' failed in ..caserverio.c
line 344
Status in EPICS Base:
Invalid
Bug description:
From Chen Zhi-chu,
I've written an ioc (using TekVISA from Tektronix on a DPO7054 Oscilloscope, Windows XP) and it starts okay at first. But when it runs for like several minutes, I got an error like:
==============================================================
A call to "assert (size <= ntohs ( pMsg->m_postsize ))" failed in ..caserverio.
c line 344.
EPICS Release EPICS R3.14.5 $R3-14-5$ $2004/02/04 20:45:33$.
Current time Fri Sep 07 2007 09:49:29.518463915 .
Please E-mail this message to the author or to [email protected]
Calling epicsThreadSuspendSelf()
==============================================================
then it stunks. I suppose that the cas_commit_msg function checks the pMsg->m_postsize and finds out it's larger than size. But I don't know how these variables come from.
I'm sorry I'm just new to EPICS and have few experiences about C
programming. Could any of you give me a clue that what's happening
now? Any input is welcome.
Original Mantis Bug: mantis-300
http://www.aps.anl.gov/epics/mantis/view_bug_page.php?f_id=300
To manage notifications about this bug go to:
https://bugs.launchpad.net/epics-base/+bug/541330/+subscriptions
- Navigate by Date:
- Prev:
[Bug 1815864] Re: Assemblies fail to work on Windows Ralph Lange via Core-talk
- Next:
[Bug 541239] Re: explicitly unloading Com.dll causes crash Andrew Johnson via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
<2019>
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
[Bug 1815864] Re: Assemblies fail to work on Windows Freddie Akeroyd via Core-talk
- Next:
[Bug 541239] Re: explicitly unloading Com.dll causes crash Andrew Johnson via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
<2019>
2020
2021
2022
2023
2024
|