Is a bracket-like construct for signal handlers possible? #149

Activity

1. cartazio commented on Mar 14, 2020

   

   cartazio

   on Mar 14, 2020

   More actions

   Ok. So are you saying that if we wanted to have a withFoo or bracketingSigfoo in Haskell user space the correct hooks aren’t exposed in the current unix/posix packaging?

   I’m relatively ignorant about these things myself.

   1. how would you write this sortah code in c ideally?

   2. what would a good wrapper / lift into Haskell look like?

   3. what’s missing to do that well?
2. jmazon commented on Mar 14, 2020

   

   jmazon

   on Mar 14, 2020

   Author

   More actions

   Judging by my local (Linux) manpages, the correct scheme in C would be:

   #include <signal.h>
   
   void mysigaction(int signo, siginfo_t *info, void *context)
   {
     /* do something */
   }
   
   int main()
   {
     struct sigaction handler, saved;
     handler.sa_handler = NULL;
     sigemptyset(&handler.sa_mask);
     handler.sa_flags = SA_SIGINFO;
     handler.sa_sigaction = mysigaction;
   
     sigaction(SIGPIPE, &handler, &saved); /* and error handling */
   
     /* later */
   
     sigaction(SIGPIPE, &saved, NULL);
     return 0;
   }

   For a low-level API, I suppose we'd just need a total information-preserving way of saving and restoring the former handler. (the current implementation seems focused on providing a way to implement signal handlers in Haskell, not on providing access to existing C ones. But I'm not convinced I understand 100% of it.)

   For a Haskell API, I'm not sure. A form of withSignalHandler sig handler action is always nice. But there's the slight catch that signals are maintained on a per-(Unix-)process basis. I'm not too sure how they relate to Haskell threads, but I wouldn't bet concurrent calls to a hypothetical withSignalHandler ended up in anything sensible.

   The current implementation doesn't appear to directly call sigaction via FFI, there's some kind of indirection through stg that rings the "it's probably more complex than seems at first" bell in my head.

   AFAIK C programs tend to set the handlers once and for all and not restore them. I ran into this essentially because of GHCi.
3. hasufell

   added

   type: enhancement

   status: info-needed

   on Jul 10, 2022