On Thu, 13 Feb 2014, marti.ma...@littlecms.com wrote: > > Obviously you are right and my description of the issue was wrong, > actually the reports I got was about an application using both lcms2 > and another library which was using lcms2 as well. The app did set > its own memory management via a plug-in, but after calling the > second library (which also set its own memory management) the > callbacks pointed to the second library mem manager and > segfaulted badly because all libs were deployed as .so and the > callbacks were pointing to hyperspace.
The IJG JPEG (starting with release 8 I think) and TIFF libraries added link-time symbol versioning to help avoid such problems. With symbol versioning, each dependent app/library gets the function/variable version compatible with the version it was linked with, even if there are several versions of the library loaded into the application. This feature works under Linux, FreeBSD, and perhaps some other OSs. Perhaps lcms should consider doing this as well, especially if it changes the major number of the library. Bob -- Bob Friesenhahn bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ ------------------------------------------------------------------------------ Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk _______________________________________________ Lcms-user mailing list Lcms-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lcms-user
