```
(gdb) c
Continuing.
^C
Program received signal SIGINT, Interrupt.
0x08000ad4 in HardFault ()
(gdb) bt
#0  0x08000ad4 in HardFault ()
#1  <signal handler called>
#2  0x0800390e in kern::arch::arm_m::syscalls::syscall_handler (syscall=<optimized out>, arg1=<optimized out>, arg2=<optimized out>, task=<optimized out>)
    at sys/kern/src/arch/arm_m/syscalls.rs:67
#3  0x08000b94 in SVCall ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) 
```

here is another flavor of the same thing

I guess the issue is it can't figure out how to unwind past a syscall / `svc` instruction

weird... I don't know why it would have trouble with that. I sometimes feel like the stack frames from cortex-m exception handlers are not handled very well by gdb