2012/6/6 Pete Batard <[email protected]>: > On 2012.06.06 15:22, Xiaofan Chen wrote: >>>> 1. libusb-1.0.dll needs to be compiled with -fno-omit-frame-pointer >>>> explicitly. Possibly it makes sense to enforce the flag in libusb's >>>> configure? >>> >>> Certainly. Do you see any problem with doing this unconditionally on >>> Windows? > > That's how I would do it as well.
Other compilers than gcc may not understand the option, but for mingw-gcc it should be safe to set -fno-omit-frame-pointer, since the option is quite old, now. >>>> 2. The files windows_usb.c and poll_windows.c contain several log >>>> statements which use the usbi_default_context. It will crash any >>>> program which does not use the default context, but an explicit >>>> context for libusb_init(). Is this a bug or a feature? > > I fully expect the recent addon of toggleable debug logging to libusbx > to take care of the issue [1]. Can you please try with the latest git > version and confirm. Libusbx-commit cf6e68a fixes the issue. A dummy call to libusb_init(NULL) fixes it, too. But according to the API docs I would expect, that any logging is done based on the particular context. So should the context be passed to usbi-functions, shouldn't it? -- Regards, Lars Kanis ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ libusbx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libusbx-devel
