"BTW, I don't think it's a signal that kills Michael's recording SoX process (but of course it would be good to know)." - here is a non-SoX fascinating example of SW failure: https://savannah.gnu.org/bugs/?60620 . As Jan said, "it would be good to know".
--Sergei.
On 14/05/2024 9:17, Jan Stary wrote:
On May 14 00:33:31, sergstesh@xxxxxxxxx wrote:"This is a SoX mailing list. Keep it that way." - well, then this: "How can I tell in Linux which process sent my process a signal <https://stackoverflow.com/questions/8400530/how-can-i-tell-in-linux-which-process-sent-my-process-a-signal>" might be useful to find out what causes SoX to terminate. But implementing this would require change in SoX source code.Of course not; there are debuggers such as ktrace and dtrace that tell you that. This has nothing to do with SoX. BTW, I don't think it's a signal that kills Michael's recording SoX process (but of course it would be good to know).For example, I saw negative results of bad SW architecture in the medical sector.Fascinating. Repreat after me: this is a SoX mailing list.
_______________________________________________ Sox-users mailing list Sox-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/sox-users
