<Yuhan Lin> cr1901: Is it possible to run "compilefail" tests for "msp430-rt" the same way it's done for "cortex-m-rt"? I tried setting it up but Xargo can't build "compilefail" at all and the Cargo can't build the main crate.
Guest2 has joined #rust-embedded
limpkin has quit [*.net *.split]
Lumpio- has quit [*.net *.split]
badboy has quit [*.net *.split]
sknebel has quit [*.net *.split]
Rahix has quit [*.net *.split]
richardeoin has quit [*.net *.split]
badboy has joined #rust-embedded
limpkin has joined #rust-embedded
sknebel has joined #rust-embedded
Lumpio- has joined #rust-embedded
Rahix has joined #rust-embedded
richardeoin has joined #rust-embedded
Yuhan Lin: I'm not sure what's wrong w/ the msp430-rt docs I'm afraid. I'll take a look this weekend or early next week
Today is not going to be a good day to look at it; docs build fine for me locally when I pass --target=msp430-none-elf -Zbuild-std=core
starblue1 has quit [Ping timeout: 240 seconds]
starblue1 has joined #rust-embedded
<dirbaio> ghidra now explodes while loading rust ELFs? "Error during DWARFAnalyzer import: ghidra.app.util.bin.format.dwarf4.DWARFException: Only DWARF version 2, 3, or 4 information is currently supported."
<adamgreig> rust's too secure for the nsa 🔒️
<dirbaio> it seems it's now generating DWARFv5 by default..?
links to a commit, but it's clang, not llvm, not sure why/how that affects rustc
<9names (@9names:matrix.org)> Run openocd through gdb so you get a stack trace when it segfaults, search their GitHub issues for similar reports, make a new one if you can't find anyone with the same error.
<omar_u8> 9names: I’m sorry but I’m not sure how to do that in gdb. Though in general, when starting gdb I’ve tried connecting to target through gdb, I get a timeout.
<omar_u8> * gdb if you can please help.
<xiretza> omar_u8: "gdb --args openocd -f interface/stlink.cfg -f target/stm32f4x.cfg" should do it - then once in the gdb shell, type "run", wait until it segfaults, then look at the output of "backtrace full"
<9names (@9names:matrix.org)> Just in case it's not clear from the error messages: openocd is crashing, so you are using gdb here to debug openocd, not your embedded program.
<9names (@9names:matrix.org)> If you aren't up for that, you can also try using a different debug tool like probe-rs-debugger or pyocd to see if that helps.