Customizable `__stack_chk_fail` implementation
Tue Oct 15 11:44:00 GMT 2019
On Tue, 2019-10-15 at 10:25 +0000, Åukasz Å»ak wrote:
> When however I build and run the same sources
> for real hardware the problems are detected - I can observe the calls
> to `__stack_chk_fail` with the gdb but as there is no semihosting
> available the write/_exit procedures used by the `__stack_chk_fail`
> handler are basically noops as they should be as on real hardware
> there is no standard output (at least in my case) and there is
> nothing to exit to.
While this is true for _write(), it's wrong for _exit(), which should
This is how a stub for _exit() should look like (code from my C++ RTOS
for ARM microcontrollers):
It may reset your chip, it may print/log whatever you want, send you an
e-mail or print something on LCD, but it should never ever return.
More information about the Newlib