Ok, I will try that. If I enable stackchecking should this kind of stack overrun be catched?
On Sun, Jun 21, 2020, at 14:22, Gregory Nutt wrote: > > > The most common cause... in fact the only cause that I am aware of ... > > for heap failure is memory corruption. > > And a very common cause of heap memory corruption is a task that has > overrun its stack and clobber the meta data at the beginning of the next > chunk. > > A simple thing you can do is to bump up stack sizes to assure this is > common case is not the cause of your problem. > >
