Re: Deadlock (busy loop) on panic/SIGSEGV case in Go API user code
Kagami Hiiragi <[email protected]>
| Newsgroups | gmane.comp.video.graphicsmagick.help |
|---|---|
| Message-ID | <[email protected]> |
Oops, accidentally sent to personal email instead of maillist. On 16/03/18 23:08, Bob Friesenhahn wrote: > On Fri, 16 Mar 2018, Kagami Hiiragi wrote: >> >> It would be even better to not set any handlers for API users at all, unless >> requested, but as you said before it might cause ABI change... > > As mentioned before, it could be handled via internal library properties which can be set prior to InitalizeMagick() without breaking the existing ABI. There would only be one or two more new functions. > > The draconian signal handlers in GM are intended to avoid leaking temporary files. Without these handlers, the using application then takes responsibility to try not to leak temporary files. > > Bob Thanks for clarification. So seems like there are three options available: 1) Add function to API to disable GM's signal handlers 2) Don't re-set Go handlers 3) Set sa_mask/sa_flags which would make Go happy Any of this is probably ok to avoid issue in question. Personally I like options 1) and 2) more. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Graphicsmagick-help mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/graphicsmagick-help