I used RISCV's fork https://github.com/riscv-mcu/riscv-openocd.
-- Best regards, Sergey Matsievskiy On Wed, 2022-04-20 at 09:42 +0100, Jonathan McDowell wrote: > On Sun, Apr 03, 2022 at 12:26:05PM +0300, Matsievskiy S.V. wrote: > > Package: openocd > > Version: 0.11.0-1 > > Severity: important > > X-Debbugs-Cc: seregaxvm.m...@gmail.com > > > > Dear Maintainer, > > > > OpenOCD segfaults when using target/stm32f1x.cfg configuration. I > > do not > > experience this issue with newer version built from source (Open > > On-Chip > > Debugger 0.11.0+dev-02226-gf6ffede8b). > > > > dmesg entry: > > [ 7388.531636] openocd[36055]: segfault at 14 ip 00007f64e097b12d > > sp > > 00007ffdde27a090 error 4 in libusb-1.0.so.0.3.0[7f64e0974000+f000] > > > > Way to reproduce: > > 1. Connect STLinkV2 > > 2. Run command openocd -f openocd.cfg (file is attached) > > I don't have STLinkV2 hardware so am unable to reproduce. Can you > confirm the upstream git version you're using - I don't see > "f6ffede8b" > in the usptream git tree. > > Also, if you're able to, can you try recompiling the 0.11.0 Debian > package on your system just to narrow down that it's a fix upstream > we're looking for rather than a build issue? I *think* it's going to > be > cff0e417da58adef1ceef9a63a99412c2cc87ff3 that's the issue, which > means > the problem won't exist in bullseye (libusb-1.0 is at 1.0.24). > > J. >
signature.asc
Description: This is a digitally signed message part
