Post AZRNHEvSX7dTCjy8mG by rain@hachyderm.io
 (DIR) More posts by rain@hachyderm.io
 (DIR) Post #AZRNHEvSX7dTCjy8mG by rain@hachyderm.io
       2023-09-05T00:34:15Z
       
       1 likes, 0 repeats
       
       Still thinking about the time I was debugging a process stopped by mdb with @bcantrill, and he mentioned continuing the process with some command (I think ::cont in mdb). I was like "oh, that's like kill -CONT" and he reacted with "we absolutely DO NOT use signals to do debugging on illumos"
       
 (DIR) Post #AZRNL4ytRtnXWJPFAm by bcantrill@mastodon.social
       2023-09-05T00:35:54Z
       
       1 likes, 0 repeats
       
       @rain  🤣  "In THIS house, under THIS roof, we do not use job control for debugging!"
       
 (DIR) Post #AZRNh2sbwU37NEwSTQ by lanodan@queer.hacktivis.me
       2023-09-05T00:48:34.284107Z
       
       0 likes, 0 repeats
       
       @bcantrill @rain Not that I would use job control for debugging but it makes me wonder why it shouldn't be done.
       
 (DIR) Post #AZROIutW51ujbzQKrw by bcantrill@mastodon.social
       2023-09-05T00:53:18Z
       
       1 likes, 0 repeats
       
       @lanodan @rain They are honestly just different ways for stopping and resuming a process; the reason to separate them is to allow them to co-exist. For more details, I would point you to seminal work of the late Roger Faulkner: https://www.usenix.org/memoriam-roger-faulkner
       
 (DIR) Post #AZRb83QLKIBIHfveJU by rain@hachyderm.io
       2023-09-05T03:16:57Z
       
       1 likes, 0 repeats
       
       @bcantrill @lanodan as a specific example, you can install a signal handler for SIGCONT and SIGTSTP (though not SIGSTOP). whatever the debugger does would ideally not cause those signal handlers to be triggered