| 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 <2016> 2017 2018 2019 2020 2021 2022 2023 2024 2025 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 <2016> 2017 2018 2019 2020 2021 2022 2023 2024 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | 答复: Question about "Link A array too large" |
| From: | lzf neu <[email protected]> |
| To: | Mark Rivers <[email protected]>, "[email protected]" <[email protected]>, Hugo Slepicka <[email protected]>, "[email protected]" <[email protected]> |
| Date: | Fri, 30 Dec 2016 01:17:17 +0000 |
|
Thanks for your respond.
Yes, it is the exact error message. however, I try to solve the problem by deleting the asyn, ipac and gensub folder respectively and change another path and recompiling them again. Now, they work well. The version of EPICS base is 3.14.12.5, ASYN is 4.9, IPAC is 2.14, gensub is 1.6 respectively. 发件人: Mark Rivers <[email protected]>
发送时间: 2016年12月29日 18:55 收件人: lzf neu 抄送: [email protected] 主题: Re: Question about "Link A array too large" What version of EPICS base, asyn, and modbus are you using? I cannot find any error messages in base 3.14.12.5 that contain the string "array too large". Is that the exact error message you are getting? Since you are getting a core dump
you can run gdb on the core file to see exactly where it is crashing.
Mark Sent from my iPhone > On Dec 28, 2016, at 9:15 AM, lzf neu <[email protected]> wrote: > > Hi all, > > I want to read real-time dose value from the radiation monitor by using epics. The driver is modbus and asyn. > > However,when starting epics ioc in server, I encounter a problem, the terminal displays something like the following information: > Link A array too large.. > Link B array too large.. > ...... > Link L array too large... > Segment fault(core dump) > > The operation system used in server is fedora20 64bit. However, the same operation system and the same modbus and asyn driver works well in my laptop connected to the monitor. > > Could you give me some suggestions to solve the problem, thanks in advanced. > |