steved wrote:Assuming that's lwIp you're running, I have a vague recollection of a similar problem. In my case it was down to insufficient stack allocation for one of the tasks; a networking-related one IIRC.
(The Chibi plugin for Eclipse will show you stack usage)
Note that you can actually use the debugger to see the states of variables at any point in the execution stack, just by highlighting the relevant level - that can sometimes give clues.
I have checked the stack usage, and I am sure that is more than sufficient (several kb more than necessary). I have also checked my heap, the exceptions stack, the main system stack... everything. I was sure that this is a memory related issue, but as it seems my memory is OK.
Giovanni wrote:The problem could be originated in another place, are you using any I-class API (those whose name ends with an "I") from thread context?
I have triple checked the code, and there are no calls to I-class functions. At all, i.e. neither in exception nor in thread context.