On 10/29/10 5:03 PM, Mark Rivers wrote:
> Folks,
>
> I am trying to run an application built for the cygwin-x86-debug
> architecture, and I am seeing a very strange behaviour. The
> application run fine, until control returns to the iocsh prompt. I
> have an epicsThreadSleep at the end of my st.cmd file, so the
> application runs for a while before I get the prompt. As soon as I get
> the prompt it appears that the EPICS threads are hung waiting for
> console input! If I keep my finger on the Enter key on the keyboard,
> so I keep sending CR characters, the application runs fine. As soon
> as I release my finger from the key the application freezes!
>
> If I had to guess what the problem was, I would suspect a problem with
> readline. Has anyone else run IOC applications under
> cygwin-x86-debug, and if so have you seen this problem?
>
> Any ideas?
Hi, Mark.
Can you try building w/out readline (e.g. COMMANDLINE_LIBRARY = EPICS)?
This will help determine whether readline is the problem, and, if
you're still trying to debug the CA problem, would let you get back to
focusing on that for now.
Lewis
- References:
- cygin-x86-debug behavior Mark Rivers
- Navigate by Date:
- Prev:
RE: cygin-x86-debug behavior Mark Rivers
- Next:
Re: cygin-x86-debug behavior Andrew Johnson
- 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
- Navigate by Thread:
- Prev:
RE: cygin-x86-debug behavior Mark Rivers
- Next:
problem with MCA module (Struck 3820 board), ACQUIRING command Jay Steele
- 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
|