hedger

Reboots with furi_check are 99.9% software issues. Please try installing latest dev firmware and see if the issue is still reproducible.

Tried multiple system configurations, couldn't reproduce. Maybe it's caused by incomplete/corrupted repo clone. Closing for now, reopen if you can provide additional logs or debugging info.

OK, I'll have a second look at this. What are the benefits of using clangd over cpptools?

FYI: furi_assert/furi_crash doesn't preserve the message if it was called from a .fap -- since we are only storing a pointer to the message string, it'll be invalid after reboot.

For better debugging experience, try using an SWD debugger - WiFi board, any ST-Link, or even a second Flipper.

Will be fixed in next release.

@dcoles should be fixed in dev & latest RC. SDK structure has changed too.

Should be fixed a few releases ago.

Please show how does your device manager display it.

When dealing with borked toolchain configuration, just remove "toolchain" directory completely. https://www.virustotal.com/gui/file/31c54186ac2aaa41a420fa78f7ff97a34e8d71e3e1dafe20b274e3ade4c1575a?nocache=1 - this is Virustotal result (0/71) for libwinpthread-1.dll from toolchain v32, in branch https://github.com/flipperdevices/flipperzero-firmware/pull/3451. Could you please check...