On 05/13/2015 03:55 PM, Mark Rivers wrote:
>> One odd thing I notice. It seems that GDB finds the debug symbols for
>> libCom, but not for libcas. It seems unlikely that this would be true
>> if both libraries were from the same build.
>
> I believe there was a problem in base that was causing debug symbols to be loaded for C code but not C++ code. It was fixed in 3.14.12.4.
I guess you mean
http://www.aps.anl.gov/epics/tech-talk/2013/msg01659.php
Which effects OPT builds, as in this case. So one of two is probably
explained. libcas contains only C++ code.
- References:
- "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy Jameson Graef Rollins
- Re: "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy Jameson Graef Rollins
- Re: "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy Michael Davidsaver
- Re: "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy Jameson Graef Rollins
- Re: "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy Michael Davidsaver
- Re: "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy Jameson Graef Rollins
- Re: "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy Michael Davidsaver
- RE: "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy Mark Rivers
- Navigate by Date:
- Prev:
RE: "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy Mark Rivers
- Next:
Re: "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy Jameson Graef Rollins
- 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: "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy Mark Rivers
- Next:
Re: "epicsMutex pthread_mutex_unlock failed" with pyepics/pcaspy Jameson Graef Rollins
- 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
|