Experimental Physics and
| |||||||||||||||
|
Hello, Can the workaround as suggested in this link https://sourceforge.net/p/linux-gpib/bugs/50/#85e8 be incorporated for the drvLinuxGpib.c in the ASYN module. The workaround suggests to mask all the signals during call to ibrd() or ibwrt() Thanks and regards, Kuldeep The text of the above link is reproduced as below "When a program receives a signal while it is in a call to a
linux-gpib driver it can happen that the application hangs. This is
because for historic reasons the linux-gpib driver framework does not
properly handle the return of -ERESTARTSYS from its device drivers.
Unfortunately to fix this systematically in the package is a lot of
work. The symptoms of a hang, due to signals, are that the program
receiving the signal hangs, blocking other programs from accessing the
device and in the console log you can find messages such as: agilent_82350b: write wait interrupted. or .../gpib/ni_usb/ni_usb_gpib.c: ni_usb_nonblocking_receive_bulk_msg: interrupted "
| ||||||||||||||
ANJ, 10 Feb 2021 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing · |