-
Notifications
You must be signed in to change notification settings - Fork 62
double free or corruption with ST-LINK/V2 #27
Comments
thank you for reporting this, but I don't maintain openocd, I just pack it and distribute for user convenience. I suggest you try the latest openocd version built from the main repository, and, if the problem is still there, report it to the maintainers. |
Oops! It might be possible that some of the RISC-V patches to interfere with ST-LINK. The RISC-V guys are cleaning their code and contributing upstream. I'll try to make a new release, hopefully it'll be less problematic. |
I just released 0.10.0-8, with the latest commits. There are many cleanups in the RISC-V code. Could you check if the problem was solved? |
I'm still getting a similar problem ... I ran OpenOCD in gdb, and also printed out the backtrace. Hope that helps .. This was done with an stm32 Nucleo 144 board. [Thread debugging using libthread_db enabled] Thread 1 "openocd" received signal SIGABRT, Aborted. #88 0x0000000000405569 in _start () |
where did you get this version? |
could you retry with the latest release (-10)? I removed most of the risc-v code, now it should not differ from the upstream version. |
I will try this with Linux and Windows version within few days. |
I can confirm that this issue is present by using
|
I just published a new release; I updated to the latest master and removed all RISC-V patches. Can you test it and confirm that the problem was solved? |
It looks like it works now |
Great, thank you! @j123b567 Jan, can you also confirm that the problem was solved, and close the ticket? |
I am suffering this behaviour in "0.10.0+dev-00392-gbe9ef0b0", the current version provided by platformio.org. @ilg-ul Which tag or commit have you applied the patch? |
in the latest release I removed all RISC-V patches, it is mostly the master repacked. the details of the builds can be seen in: https://github.com/gnu-mcu-eclipse/openocd-build/blob/master/scripts/container-build.sh |
False alarm: uC is damaged and OpenOCD binary dumps, but this is another story... Ignore my comment since it is not related to this issue... Thanks anyway :-) |
I just released 0.10.0-12, with the latest upstream master. Please check if the problem was solved. If not, reopen the ticket. |
Description
I have board without hardware reset and when I accidentaly configure
reset_config srst_only
, openocd failes with "double free or corruption".I can connect with ST-LINK/V2-1 without problem.
(ST-LINK/V2-1 is reported as
STLINK v2 JTAG v30 API v2 SWIM v20 VID 0x0483 PID 0x374B
)After connecting with ST-LINK/V2, OpenOCD fails with backtrace and double free or corruption message.
(ST-LINK/V2 is reported as
STLINK v2 JTAG v30 API v2 SWIM v7 VID 0x0483 PID 0x3748
)I have tried all versions of gnu-mcu-eclipse/openocd and the problem was not in version
v0.10.0-2-20170622-1535-dev
and it first occures in
v0.10.0-3-20170826-1813-dev
all later versions are affected, at least
v0.10.0-7-20180123
v0.10.0-5-20171110
Steps to Reproduce
Expected behaviour: [What you expected to happen]
Actual behaviour: [What actually happened]
Versions
The text was updated successfully, but these errors were encountered: