Control: tags -1 + confirmed On Fri, 2017-07-14 at 23:08 +0200, László Böszörményi wrote: > There's a chance that on some signals (including, but not limited to > SIGSEGV) socat goes to an infinite loop and consume all CPU cycles. > Upstream patched it[1] for 1.7.3.2 release, which is in Sid. Basically > set 'diag_immediate_exit' in the signal handling function to let it > exit. Full debdiff is attached. > > Thanks for considering, > Laszlo/GCS > [1] > http://repo.or.cz/socat.git/commitdiff/6b596b8852d8fad2675894e3ceb18a04801eaf23?hp=d34493c18df0a4d0c4fdb5bda74a155ce13e4ccf
Please go ahead. Regards, Adam