so the results of a week of investigation are: libusb-1.0.15 compiled with clang on MacOS 10.8 lead to a segmentation fault on MacOS 10.6 libusb-1.0.15 compiled with gcc4.2 on MacOS 10.6 works as expected on MacOS 10.6 && MacOS 10.8
the user have installed XCode 3.something (the last available for 10.6), compiled the lib for both 32 and 64 bits and this one does not segfault. I thought you must knew. ++ Nicolas Le 25/04/13 13:15, Ludovic Rousseau a écrit : > 2013/4/24 NicoBats <sl1200...@gmail.com>: >> Hi, > Hello, > >> today a user report a segmentation fault on MacOS 10.6. >> I'm compiling libusbx on MacOS 10.8 like that >> export CXX=/usr/bin/clang++ >> export CC=/usr/bin/clang >> export >> PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/X11/bin:/usr/X11/include:/sw/bin:/sw/sbin:/opt/local/bin:/opt/local/sbin >> export PKG_CONFIG_PATH="/opt/local/lib/pkgconfig:$PKG_CONFIG_PATH" >> ./configure --enable-debug-log --enable-examples-build --enable-tests-build >> make CFLAGS="-arch i386 -arch x86_64 -mmacosx-version-min=10.6" >> >> and here's the log form the user: >> [timestamp] [threadID] facility level [function call] <message> >> ________________________________ >> [ 0.003674] [00000903] libusbx: debug [libusb_get_device_list] >> Segmentation fault >> $ >> >> nothing more... >> the crash log looks like this: >> >> Date/Time: 2013-04-24 17:05:10.504 +0200 >> OS Version: Mac OS X 10.6.8 (10K549) >> Report Version: 6 >> >> Exception Type: EXC_BAD_ACCESS (SIGSEGV) >> Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000 >> Crashed Thread: 0 Dispatch queue: com.apple.main-thread >> >> Thread 0 Crashed: Dispatch queue: com.apple.main-thread >> 0 libusb-1.0.0.dylib 0x00000001008e6914 usb_get_next_device + >> 1236 >> 1 libusb-1.0.0.dylib 0x00000001008e25b4 darwin_get_device_list >> + 100 >> 2 libusb-1.0.0.dylib 0x00000001008daf2d libusb_get_device_list >> + 141 >> 3 DLight 0x000000010000e787 ftdi_usb_find_all + 39 >> 4 DLight 0x000000010004d583 libUSB_Connect + 275 >> >> >> is there is a simple way on MacOSX to try >> ./ xusb -i 0403:6001 >> >> >> Does the user need to install XCode in order to compile libusbx to see if I >> fail at compilation? > If the compilation succeeds it should be OK. > You can add debug information by adding "-g": > CFLAGS="-g ..." > > We can then get some more debug information in the crash log. > > Bye > > -- > Dr. Ludovic Rousseau > > ------------------------------------------------------------------------------ > Try New Relic Now & We'll Send You this Cool Shirt > New Relic is the only SaaS-based application performance monitoring service > that delivers powerful full stack analytics. Optimize and monitor your > browser, app, & servers with just a few lines of code. Try New Relic > and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr > _______________________________________________ > libusbx-devel mailing list > libusbx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/libusbx-devel ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
