I use the latest FTDI driver. With new configs it still crashes. Under valgrind it doesn't crash but prints errors you can find in attachment.
19.06.2013, 19:08, "Andreas Fritiofson" <[email protected]>: > On Wed, Jun 19, 2013 at 4:11 PM, Paul Fertser <[email protected]> wrote: >> Hi, >> >> On Wed, Jun 19, 2013 at 02:44:24PM +0400, Alexander Pakhomov wrote: >>> pahom@pahom-ThinkPad-X220:~/trunk/root_bk/jtag$ sudo gdb -q -args >>> ~/bin/bin/openocd -f armusbocd_tiny.cfg -f stm32f4x.cfg >> >> Please use the newer ftdi driver and the corresponding config file >> "interface/ftdi/olimex-jtag-tiny.cfg", as it's important to have >> proper config files in the upstream sources; and if you have any >> issues with it, feel free to report. > > The stock target/stm32f4x.cfg should be usable as it is, too. > >>> *** glibc detected *** /home/pahom/bin/bin/openocd: double free or >>> corruption (!prev): 0x08273df8 *** >>> ======= Backtrace: ========= >>> /lib/i386-linux-gnu/libc.so.6(+0x75ee2)[0xb7e6bee2] >>> /home/pahom/bin/bin/openocd[0x8148439] >>> /home/pahom/bin/bin/openocd[0x8156cb2] >>> /home/pahom/bin/bin/openocd[0x815545e] >> >> I think if you do something like >> >> l *0x8148439 >> l *0x8156cb2 >> l *0x815545e >> >> in gdb to see the source code corresponding to those addresses, it >> will help debugging the issue considerably. > > Or better, just do a bt to get a separate backtrace from gdb which should > contain the necessary information already. The limited auto-printed backtrace > is from libc. > > It may also help to have a -d3 debug log. > > /Andreas
val_out
Description: Binary data
------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev
_______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
