2013/9/7 Hans de Goede <hdego...@redhat.com>: > Well, alternatively we could document that libusb-compat uses atexit for > cleanup, > and that apps using it should either not access libusb from their own atexit > handlers, > or register their atexit handler after calling libusb_init (atexit handlers > are > called in reverse registration order).
If we ask maintainers to modify the code of their application using libusb-0.1 we should just tell the to use libusb-1.0 directly. The goal of libusb-compat is to allow "unmaintained" applications using the libusb-0.1 API to benefit from libusb-1.0 with no code change. We should not break this "contract". So I think the best is to keep the resource leak and avoid crashes. Bye -- Dr. Ludovic Rousseau ------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clktrk _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
