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. > *** 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. HTH -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:[email protected] ------------------------------------------------------------------------------ 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
