Thanks @nerditation ,
Yes, must be an oversized future. Sounds like a probable hypothesis. But...
How can I track this down? Does it make sense to look into the ELF file?See update below.This is a hard fault in safe code... Isn't Rust supposed to catch that kind of error?Nope - not for stack overflows.
UPDATE: Confirmed - As stack allocations in the pre-amble always follow the same pattern it's easy to see which function allocates what. By looking at the SP offsets I can estimate variable/future size. That works.