Yeah, probably I have triggered some but in libusb / freebsd usb stack :-( According to enormous backtrace history this may be one of the race conditions Peter is fighting against...?
There is as much information on this: http://pastebin.com/wp3ng0n4 The interesting is that stuff on my fork works fine even on older FreeBSD 8.1 ! Probably I stripped to much stuff, or has changed since I started my fork. My FreeBSD 8.2 is up to date. Will download and install Arch linux and try on that one, then let you know afternoon (I wont install ubuntu as this is evil and will not work without replacing my bootloader to grub2 lol). On Thu, Jun 16, 2011 at 8:53 AM, Xiaofan Chen <xiaof...@gmail.com> wrote: > On Thu, Jun 16, 2011 at 4:20 PM, Tomek CEDRO <tomek.ce...@gmail.com> wrote: >> Did anyone had similar problem? >> >> Was anything changed recenlty in the code regarding >> usb/libusb/libftdi/ft2232? >> >> Program received signal SIGSEGV, Segmentation fault. >> 0x281eaf67 in libusb20_dev_get_speed () from /usr/lib/libusb.so.2 > > This library is only for FreeBSD. I know this from the name libusb20. > libusb and libusb-1.0 on FreeBSD 8.0 and later are just wrapper > on top of the FreeBSD libusb20 library. > >> (gdb) bt >> #0 0x281eaf67 in libusb20_dev_get_speed () from /usr/lib/libusb.so.2 >> #1 0x281e5357 in usb_get_descriptor_by_endpoint () from /usr/lib/libusb.so.2 >> #2 0x281de7ad in ftdi_write_data () from /usr/local/lib/libftdi.so.18 >> #3 0x0808a010 in ft2232_write (buf=0xbfbfd8c9 "\200", size=3, >> bytes_written=0xbfbfd8bc) at ft2232.c:531 >> #4 0x0808a2c8 in ft2232_bitbang (device=0x0, signal_name=0x819bfa0 >> "led", GETnSET=0, value=0x28455308) at ft2232.c:660 >> #5 0x08055d56 in handle_bitbang_command (cmd=0xbfbfd934) at bitbang.c:126 > > > I tend to think this may well be a FreeBSD libusb issue. > You may want to add USB debug information. And you may > also want to update to the latest FreeBSD kernel. I no longer > try to use FreeBSD myself. > > > -- > Xiaofan > -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
