Experimental Physics and Industrial Control System
|
A bit of luck. By chance I typed 'pvinfo' when I meant to type 'pvget'
and replicated this issue. It is a race. I have fixed it in the pvtools
rewrite. Please update and retest.
> cd modules/pvAccess
> git fetch md
> git reset --hard md/pvtoolsrework
> cd ../..
> make
https://github.com/epics-base/pvAccessCPP/pull/129
On 10/29/18 11:52 AM, Kasemir, Kay wrote:
>> Can you do a -debug build?
>> cat <<EOF >>configure/CONFIG_SITE.local
>> CROSS_COMPILER_TARGET_ARCHS+=\$(EPICS_HOST_ARCH)-debug
>> EOF
>> make
>> Then run in gdb:
>> gdb --args ./bin/linux-x86_64-debug/pvinfo TST:iq
>> b clientContextImpl.cpp:4679
>> r
>> # this break should be reached on success or failure. when it is reached.
>
> Isn't getting to that breakpoint.
>
> $ pvget training:ai1
> training:ai1 2018-10-29T14:46:34.573 2 MAJOR DEVICE LOLO
>
> $ pvinfo training:ai1
> training:ai1 Error: channel destroyed
>
> $ gdb --args bin/linux-x86_64-debug/pvinfo training:ai1
> GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-110.el7
> Copyright (C) 2013 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law. Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "x86_64-redhat-linux-gnu".
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>...
> Reading symbols from /home/training/epics-train/tools/epics-base/bin/linux-x86_64-debug/pvinfo...done.
> (gdb) b clientContextImpl.cpp:4679
> No source file named clientContextImpl.cpp.
> Make breakpoint pending on future shared library load? (y or [n]) y
> Breakpoint 1 (clientContextImpl.cpp:4679) pending.
> (gdb) r
> Starting program: /home/training/epics-train/tools/epics-base/bin/linux-x86_64-debug/pvinfo training:ai1
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib64/libthread_db.so.1".
> [New Thread 0x7ffff554f700 (LWP 10492)]
> [Thread 0x7ffff554f700 (LWP 10492) exited]
> [New Thread 0x7ffff7fd7700 (LWP 10493)]
> [New Thread 0x7ffff7f56700 (LWP 10494)]
> [New Thread 0x7ffff7ed5700 (LWP 10495)]
> [New Thread 0x7ffff4b3b700 (LWP 10496)]
> [New Thread 0x7ffff4aba700 (LWP 10497)]
> [New Thread 0x7ffff4a39700 (LWP 10498)]
> [New Thread 0x7ffff49b8700 (LWP 10499)]
> [New Thread 0x7ffff554f700 (LWP 10502)]
> [New Thread 0x7ffff46b5700 (LWP 10503)]
> [Thread 0x7ffff7fd7700 (LWP 10493) exited]
> training:ai1 Error: channel destroyed
> [Thread 0x7ffff554f700 (LWP 10502) exited]
> [Thread 0x7ffff7f56700 (LWP 10494) exited]
> [Thread 0x7ffff7ed5700 (LWP 10495) exited]
> [Thread 0x7ffff4b3b700 (LWP 10496) exited]
> [Thread 0x7ffff4aba700 (LWP 10497) exited]
> [Thread 0x7ffff4a39700 (LWP 10498) exited]
> [Thread 0x7ffff46b5700 (LWP 10503) exited]
> [Thread 0x7ffff49b8700 (LWP 10499) exited]
> [Inferior 1 (process 10488) exited with code 01]
>
>
> -Kay
>
- Replies:
- Re: pvget -m timeout after first value Kasemir, Kay via Core-talk
- References:
- pvget -m timeout after first value Kasemir, Kay via Core-talk
- Re: pvget -m timeout after first value Michael Davidsaver
- Re: pvget -m timeout after first value Kasemir, Kay via Core-talk
- Re: pvget -m timeout after first value Michael Davidsaver
- Re: pvget -m timeout after first value Kasemir, Kay via Core-talk
- Re: pvget -m timeout after first value Michael Davidsaver
- Re: pvget -m timeout after first value Kasemir, Kay via Core-talk
- Re: pvget -m timeout after first value Michael Davidsaver
- Re: pvget -m timeout after first value Kasemir, Kay via Core-talk
- Re: pvget -m timeout after first value Michael Davidsaver
- Re: pvget -m timeout after first value Kasemir, Kay via Core-talk
- Re: pvget -m timeout after first value Kasemir, Kay via Core-talk
- Re: pvget -m timeout after first value Michael Davidsaver
- Re: pvget -m timeout after first value Kasemir, Kay via Core-talk
- Re: pvget -m timeout after first value Michael Davidsaver
- Re: pvget -m timeout after first value Kasemir, Kay via Core-talk
- Navigate by Date:
- Prev:
Jenkins build is back to normal : epics-7.0-windows » DLL,win64 #63 APS Jenkins via Core-talk
- Next:
Re: pvget -m timeout after first value Kasemir, Kay 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:
Re: pvget -m timeout after first value Kasemir, Kay via Core-talk
- Next:
Re: pvget -m timeout after first value Kasemir, Kay 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
|
ANJ, 30 Oct 2018 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
·
Search
·
EPICS V4
·
IRMIS
·
Talk
·
Bugs
·
Documents
·
Links
·
Licensing
·
|