Below issue was reported [1] in socat: Socats signal handler implementations are not asnyc-signal-safe. When a signal is triggered while the process is within a non async-signal-safe function the signal handler will call a non sync-signal-safe function too. POSIX specifies the behaviour in this situation as undefined. Dependend on involved functions, libraries, and operating system, the process can continue, freeze, or crash. Mostly this issue occurs when socat is in listening mode with fork option and a couple of child processes terminate at the same time. [1]: http://www.dest-unreach.org/socat/contrib/socat-secadv6.txt
Created socat tracking bugs for this issue: Affects: fedora-all [bug 1185945] Affects: epel-all [bug 1185946]
This should be a dupe of bug 1185711.
*** This bug has been marked as a duplicate of bug 1185711 ***
(In reply to Tomas Hoger from comment #2) > This should be a dupe of bug 1185711. Yes, it is. Thanks for catching this.