On Wed, Jun 6, 2012 at 10:12 PM, Peter Stuge <[email protected]> wrote: > Lars Kanis wrote: >> I maintain the libusb-1.0-binding for Ruby ( >> https://github.com/larskanis/libusb ). The precompiled version for >> Windows is built from libusb-1.0.9 sources with 32 bit version of >> mingw-w64-2.0.1 and gcc-4.6.3 on Ubuntu 12.04. Recently I noticed two >> issues, I would like to discuss. > > Thanks for the report! > >> 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? > > >> 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? > > This is a bug. > > > Xiaofan Chen wrote: >> I have added libusbx to the CC. libusbx is the where the >> main Windows development will happen since Pete is the >> main driver for it and he does not usually read libusb-devel. > > Xiaofan, Pete is not the only person who can fix problems in the > Windows backend. All libusb bugs are of course taken seriously, > regardless of where in the code they are. > >
That is certainly true. On the other hand, it is also good to discuss in both lists so I think adding CC to libusbx is not a problem. -- Xiaofan ------------------------------------------------------------------------------ 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
