MSVC v1.0.0 Crash during probe switch / firmware update for common targets variant #65

DavidKeizerFA commented 2025年10月06日 20:01:22 +02:00 (Migrated from github.com)

When attempting to switch variants, or force a firmware update on a Black Magic Probe 2.0.0 to the "common targets" firmware variant, the executable crashes with the following output:

bmputil-cli.exe probe update -f
⠁ Updating release metadata cache ⠉ Updating release metadata cache ⠙ Updating release metadata cache ⠚ Updating release metadata cache ⠒ Updating release metadata cache ⠂ Updating release metadata cache ⠂ Updating release metadata cache ⠒ Updating release metadata cache ⠲ Updating release metadata cache ⠴ Updating release metadata cache Updating release metadata cache [2025年10月06日T17:46:12Z INFO bmputil::metadata] Validating v1 metadata with 18 releases present
[2025年10月06日T17:46:12Z WARN bmputil_cli] Forcibly downgrading firmware from 2.0.0 to 2.0.0
✔ Which firmware variant would you like to run on your probe? · Black Magic Debug for BMP (common targets)
✔ What action would you like to take with this firmware? · Flash to probe
Error: ------------[ ✂ cut here ✂ ]------------
Unhandled crash in bmputil-cli v1.0.0
 0: bad offset 1229968
 1: bad offset 1229968
Location:
 src/elf.rs:66
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 1: onig_get_start_by_callout_args<unknown>
 at <unknown source file>:<unknown line>
 2: onig_builtin_mismatch<unknown>
 at <unknown source file>:<unknown line>
 3: onig_builtin_mismatch<unknown>
 at <unknown source file>:<unknown line>
 4: onig_builtin_mismatch<unknown>
 at <unknown source file>:<unknown line>
 5: onig_builtin_mismatch<unknown>
 at <unknown source file>:<unknown line>
 6: onig_unicode_define_user_property<unknown>
 at <unknown source file>:<unknown line>
 7: BaseThreadInitThunk<unknown>
 at <unknown source file>:<unknown line>
 8: RtlUserThreadStart<unknown>
 at <unknown source file>:<unknown line>

Remarks:

• The probe was previously running an older release, but I do not recall which version, and was initially updated to v2.0.0 for ST and ST-clones firmware variant.
• Flashing the RISC-V variant succeeds, but I do get the following: ERROR nusb::platform::windows_winusb::device] WinUsb_ControlTransfer failed: A device attached to the system is not functioning. (os error 31). This may not be related.
• Flashing back to the ST and ST-clones targets behaves the same as the RISC-V variant.
• Flashing to the common target variant always fails with the above crash.
• The crash is the same for bmputil-cli.exe probe update -f and bmputil-cli.exe probe switch.
• OS is Windows 10 20H2 (19042.2728)

When attempting to switch variants, or force a firmware update on a Black Magic Probe 2.0.0 to the "common targets" firmware variant, the executable crashes with the following output: ``` bmputil-cli.exe probe update -f ⠁ Updating release metadata cache ⠉ Updating release metadata cache ⠙ Updating release metadata cache ⠚ Updating release metadata cache ⠒ Updating release metadata cache ⠂ Updating release metadata cache ⠂ Updating release metadata cache ⠒ Updating release metadata cache ⠲ Updating release metadata cache ⠴ Updating release metadata cache Updating release metadata cache [2025年10月06日T17:46:12Z INFO bmputil::metadata] Validating v1 metadata with 18 releases present [2025年10月06日T17:46:12Z WARN bmputil_cli] Forcibly downgrading firmware from 2.0.0 to 2.0.0 ✔ Which firmware variant would you like to run on your probe? · Black Magic Debug for BMP (common targets) ✔ What action would you like to take with this firmware? · Flash to probe Error: ------------[ ✂ cut here ✂ ]------------ Unhandled crash in bmputil-cli v1.0.0 0: bad offset 1229968 1: bad offset 1229968 Location: src/elf.rs:66 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1: onig_get_start_by_callout_args<unknown> at <unknown source file>:<unknown line> 2: onig_builtin_mismatch<unknown> at <unknown source file>:<unknown line> 3: onig_builtin_mismatch<unknown> at <unknown source file>:<unknown line> 4: onig_builtin_mismatch<unknown> at <unknown source file>:<unknown line> 5: onig_builtin_mismatch<unknown> at <unknown source file>:<unknown line> 6: onig_unicode_define_user_property<unknown> at <unknown source file>:<unknown line> 7: BaseThreadInitThunk<unknown> at <unknown source file>:<unknown line> 8: RtlUserThreadStart<unknown> at <unknown source file>:<unknown line> ``` Remarks: - The probe was previously running an older release, but I do not recall which version, and was initially updated to v2.0.0 for ST and ST-clones firmware variant. - Flashing the RISC-V variant succeeds, but I do get the following: `ERROR nusb::platform::windows_winusb::device] WinUsb_ControlTransfer failed: A device attached to the system is not functioning. (os error 31)`. This may not be related. - Flashing back to the ST and ST-clones targets behaves the same as the RISC-V variant. - Flashing to the common target variant always fails with the above crash. - The crash is the same for `bmputil-cli.exe probe update -f` and `bmputil-cli.exe probe switch`. - OS is Windows 10 20H2 (19042.2728)