As it seems, adding the flag -ffixed-r10 solves my initial problem. The
application runs normally, and detects any overflows.
However, indeed __stack_overflow_trap is misbehaving. Although it is
declared with __attribute__((naked, no_instrument_function)), it seems that
GCC is not respecting it.
I just spent some time on this.
It is a false alarm, and seems not related to #1900.
It only happens if I have optimizations enabled. On some builds it also
happens on other functions than the aforementioned one.
It is caused by R10 contents getting corrupted. Then I realized that I need
to add t
Hi Fotis,
>NuttX is not able to boot at all with this option selected. I stepped
>through the code and it seems that nxsig_initialize actually causes a stack
>overflow that is detected by the above check.
>Is this a bug, or I should configure something in a different way?
Have you seen
https://c
Hi,
I've been nearly completely out of order for the last week and a half, and I
still have to fix #1900.
Since your issue could be related:
Is nxsig_initialize really causing a stack overflow in your case, or is it a
false positive?
Johannes
> -Original Message-
> From: Fotis Panagiot
