finally i find it's usleep call causes that
while(retry && ((RCC_BDCR & 0x02) == 0)) // External low-speed oscillator
> ready
> {
> retry--;
>
> usleep(5000);
> #if 0
> volatile int k = 0;
> (void)k;
> int j;
> for(j = 0; j < 1000; j++)
> k = k + 1;
> #endif
> }
>
On Wed, May 22, 2019 at 2:54 AM Gedare Bloom <[email protected]> wrote:
> This just covers up some bug. When the system overhead increased to check
> the stack contents, it might modify the timing enough to obscure a race
> condition. Since the stack checker didn't report anything, you probably
> don't have a blown task stack. (But you could still have a function stack
> overflow.)
>
>
> On Fri, May 17, 2019, 4:21 AM Jython <[email protected]> wrote:
>
>> thanks a lot!
>> when i add #define CONFIGURE_STACK_CHECKER_ENABLED
>> problem disappeared, but i still dont understand how it happend
>>
>> On Fri, May 17, 2019 at 6:00 PM Sebastian Huber <
>> [email protected]> wrote:
>>
>>> On 17/05/2019 11:58, Jython wrote:
>>> > hi, Huber! how to debug general stack corruption?
>>>
>>> The first thing is to turn on the stack checker.
>>>
>>> --
>>> Sebastian Huber, embedded brains GmbH
>>>
>>> Address : Dornierstr. 4, D-82178 Puchheim, Germany
>>> Phone : +49 89 189 47 41-16
>>> Fax : +49 89 189 47 41-09
>>> E-Mail : [email protected]
>>> PGP : Public key available on request.
>>>
>>> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
>>>
>>> _______________________________________________
>> users mailing list
>> [email protected]
>> http://lists.rtems.org/mailman/listinfo/users
>
> _______________________________________________
> users mailing list
> [email protected]
> http://lists.rtems.org/mailman/listinfo/users
_______________________________________________
users mailing list
[email protected]
http://lists.rtems.org/mailman/listinfo/users
