ChanServ changed the topic of #rust-embedded to: Welcome to the Rust Embedded IRC channel! Bridged to #rust-embedded:matrix.org and logged at https://libera.irclog.whitequark.org/rust-embedded, code of conduct at https://www.rust-lang.org/conduct.html
cinemaSundays has joined #rust-embedded
starblue has quit [Ping timeout: 260 seconds]
starblue has joined #rust-embedded
cinemaSundays has quit [Quit: Connection closed for inactivity]
richardeoin has quit [Ping timeout: 252 seconds]
richardeoin has joined #rust-embedded
ana_briated has quit [Ping timeout: 260 seconds]
pcs38 has joined #rust-embedded
sroemer has joined #rust-embedded
sroemer has joined #rust-embedded
sroemer has quit [Changing host]
pcs38 has quit [Quit: leaving]
tk has quit [Remote host closed the connection]
tk has joined #rust-embedded
pcs38 has joined #rust-embedded
AlexandrosLiarok has joined #rust-embedded
<AlexandrosLiarok> any good way to print the "current" stack register surviving at release builds ?
balbi[m] has quit [Quit: Idle timeout reached: 172800s]
zeenix[m] has quit [Quit: Idle timeout reached: 172800s]
JamesMunns[m] has joined #rust-embedded
<JamesMunns[m]> You mean the current stack pointer?
<JamesMunns[m]> You can read the msp or psp through the cortex-m crate: https://docs.rs/cortex-m/latest/cortex_m/register/index.html
pcs38 has quit [Quit: leaving]