On Sat, Apr 28, 2012 at 4:14 PM, Freddie Chopin <[email protected]> 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? > > 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. http://sourceforge.net/mailarchive/forum.php?thread_name=4FA9A0A7.80301%40akeo.ie&forum_name=libusbx-devel http://libusbx.git.sourceforge.net/git/gitweb.cgi?p=libusbx/libusbx;a=commit;h=1ed09c7b2a5fc27c3cfea21740584879781bff67 > The debug log: > http://dstrtc.linuxpl.info/log.7z > > Divisor vaules and calculations seem to be OK. > > So - any hints about GDB? -- 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/ _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
