Xiaofan Chen wrote: > > I've tried running OpenOCD in GDB to get the backtrace, but when I cause > > the crush and do "bt full" I just see: > >> (gdb) bt full > >> #0 0x00000000771e3560 in ntdll!RtlAppendStringToString () > >> from C:\Windows\system32\ntdll.dll > >> No symbol table info available. > >> #1 0x0000000000000000 in ?? () > >> No symbol table info available. > > > > What am I doing wrong? The binary was not stripped, maybe I need to > > compile OpenOCD in some other way?
How was OpenOCD compiled, and how were the reverse library dependencies compiled? > > Maybe the problem is somehow related to the fact that I'm using > > 64-bit Windows 7? The 32-bit binary crushes anyway... > > It may have something to do with libusbx-1.0.10. You > may want to try out libusbx-1.0.11. > > Both libusb-1.0.9 and libusbx-1.0.10 have a serious > bug under Windows. The mpsse driver is unaffected by the bug. The bug only affects applications which call into libusb event handling from one thread and submit transfers from another. > > So - any hints about GDB? I suggest setting a few strategic breakpoints and then stepping manually through the code. //Peter ------------------------------------------------------------------------------ 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/ _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
