Re: Deadlock (busy loop) on panic/SIGSEGV case in Go API user code
Bob Friesenhahn <[email protected]>
| Newsgroups | gmane.comp.video.graphicsmagick.help |
|---|---|
| Message-ID | <[email protected]> |
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 -- Bob Friesenhahn [email protected], http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot