I don't know if it is the same for all the previous crashes...
however the effects are the same...
Hi Dariush,
The gdb backtrace says that the crash is actually in the Linux
readline library. Was this crash caused by the same sequence of
events as previous crashes you observed?
Mark
Hi Mark,
Are you using a Dante1 or a Dante8?
I'm using Dante8
Does this happen every time you start, or just occasionally. If
it is occasionally, then how frequently does it happen?
Occasionally, more often when I two records are executed very
closely
Are there any error messages on the IOC?
no, however some records are in "acquire" exit (as $(P)$(M).ACQG
in mca window)
Are you running on Linux or Windows?
Linux (Centos 9)
If you are running on Linux then please run the IOC in the GNU
debugger. You can do that with the following commands from the
iocDante1 directory:
gdb ../../bin/linux-x86_64/mcaDanteApp
run st.cmd
When it crashes type this command at the debugger prompt:
backtrace
(gdb) backtrace
#0 0x00007ffff5904b92 in pselect () from /lib64/libc.so.6
#1 0x00007ffff6b143bb in rl_getc () from
/lib64/libreadline.so.8
#2 0x00007ffff6b13cd1 in rl_read_key () from
/lib64/libreadline.so.8
#3 0x00007ffff6af8497 in readline_internal_char () from
/lib64/libreadline.so.8
#4 0x00007ffff6b01535 in readline () from
/lib64/libreadline.so.8
#5 0x00007ffff6c85cd2 in osdReadline (context=0x444dc0,
prompt=0x7ffff6c9c183 "epics> ") at
../osi/os/default/gnuReadline.c:70
#6 epicsReadline (prompt=0x7ffff6c9c183 "epics> ",
context=0x444dc0) at ../osi/epicsReadline.c:68
#7 0x00007ffff6c77aea in iocshBody (pathname=<optimized
out>, commandLine=0x0, macros=0x0) at ../iocsh/iocsh.cpp:1143
#8 0x000000000040a616 in main (argc=<optimized out>,
argv=<optimized out>) at ../mcaDanteAppMain.cpp:20
Thank you in
advance
Dariush e Maurizio
Il 16/06/2026
18:18, Mark Rivers ha scritto:
Hi Dariush,
Are you using a Dante1 or a Dante8?
Does this happen every time you start, or just occasionally.
If it is occasionally, then how frequently does it happen?
Are there any error messages on the IOC?
Are you running on Linux or Windows?
If you are running on Linux then please run the IOC in the GNU
debugger. You can do that with the following commands from the
iocDante1 directory:
gdb ../../bin/linux-x86_64/mcaDanteApp
run st.cmd
When it crashes type this command at the debugger prompt:
backtrace
Send me the output.
Mark
Hi Community,
Hi Mark,
I'm almost finish the implementation of Dante EPICS Drivers in
our
system, however I have a big problem (maybe a bug?).
When I start few acquisitions (from caput command or from
Phebus), the
system seems that crash.
The Dante:dante2:ElapsedRealTime stops (not on target).
Moreover on
Phebus the text is in "Collecting" mode, The Acquire Busy is
in
"Acquiring" mode and the IOC do not respond to any command
that I send.
Up to now, the only solution is to stop the IOC and restart
it.
What's the problem?
Is there a possibility to force a reset/reinitialize the
driver without
stop and restart it?
awaiting your (precious) help
Dariush
--
************************************
Dr. Dariush Hampai, PhD
INFN - LNF
X-Lab Frascati
Via E. Fermi, 54 (ex 40)
I-00044 Frascati (RM)
Italy
Mail Address:
XLab-Frascati
LNF-INFN
Casella Postale 13
Frascati (RM)
Italy
Room: +39.06.9403.5248
Lab.: +39.06.9403.2286
Mob.: +39.06.9403.8025
Fax.: +39.06.9403.2597
************************************