Closed taylorh140 closed 1 month ago
So I took the folder from windows after d.ps1 executed and moved it to my linux setup. And got the same problem. So this is actually probably a problem with the d.ps1 and maybe not with the rust code.
./d.ps1 is pulling embassy-rs/stm32-data-sources@74b97817d4c4ed0db9d19a8eac46720b3c5b0d57 (April 12) but
./d is pulling embassy-rs/stm32-data-sources@709c1060ac2ec57f6042f2b4eb9cf8c1821a6c57 (April 29)
Manually pulling embassy-rs/stm32-data-sources@709c1060ac2ec57f6042f2b4eb9cf8c1821a6c57 or embassy-rs/stm32-data-sources@1a3751550575f8ffee5e45307713a3e08bc9ffb4 (Jun 7) fixes the build.
This is good advice.
To reproduce grab the present main and build on a window machine. You should get this error. It has something to do with the fmt ? maybe?
STATUS_STACK_BUFFER_OVERRUN
seems bad.
Might be relevent: https://users.rust-lang.org/t/status-stack-buffer-overrun/34873
It would match the story about the "println(...{:?}..., something);" causing issues. as fmt seems to be at the root of the call stack.