RE: StreamDevice/AsynIPPort question

[Mark Rivers <rivers@cars.uchicago.edu>]

Hi Michael,

 

Is the IOC running on Linux?  If so you can use the following commands to figure out where it is crashing.

 

On bash shell:

ulimit -c 10000000

 

or on csh shell:

limit core 1000000

 

Then run the IOC application.  When it crashes it will create a core.xxxxxx file.

 

Then run the Gnu debugger:

 

gdb path/to/your/IOC/executable core.xxxxxx

 

You need to provide the path to your IOC executable and replace core.xxxxxx with the name of the core file it just created.

 

Mark

 

 

From: tech-talk-bounces@aps.anl.gov [mailto:tech-talk-bounces@aps.anl.gov] On Behalf Of Michael Westfall
Sent: Thursday, November 10, 2016 2:31 PM
To: tech-talk@aps.anl.gov Talk
Subject: StreamDevice/AsynIPPort question

 

We are having problems with IOC crashing when a device connected by an IP socket is unavailable.

For example, in the startup script is a line like:

drvAsynIPPortConfigure("temp", "172.16.5.218:10010")

and a StreamDevice record that uses that IP port when it calls it's protocol.

 If we unplug the ethernet cable from the device (or just power it off) the IOC crashes after a short while. No error is emitted on the console  to indicate that the connection has failed.

So, I'm wondering if there is something we need to do in setting up the AsynIPPort  or the StreamDevice protocol file in order to gracefully handle the case where the socket disappears and can't be reconnected to....

Thanks,

--

Mike Westfall

Control Systems Software Engineer