- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
While attempting to debug an 802.1X connection to FreeRADIUS I enabled the DEBUG define in an attempt to get more information regarding the problems we were encountering. The result was a stack overflow error. This was picked up in ThreadX.
The application we were running the standard console program included in the SDK. This running under WICED 4.0.0
The assert stop the program
I have tried to increase both the ThreadX stack allocation - up to 4K and the app up to 8K with out any change. It seems something is going wrong elsewhere that causes a problem in ThreadX
Thanks
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Are you use mini printf?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
no, but as you can see this is not in a routine calling printf
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I dont known how closed source treadx checking stack overflow. FreeRtos checking when swithing context. Possible printf calling in other thread. Maybe parameter TX_THREAD *thread show which thread overflow stack?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Looking at the data for the thread it seems that the stack has not overflowed
This is the details of the thread structure in the failed routine - I increased the stack size to 8K in the thread definition but the start and end difference is only 6139
I do not understand why this is occuring
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Enlarging Stack to 10K resolves this particular issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I would have thought that stack overflow would be trapped by default. It was a painful learning that it is not enabled by default.
Is there much of a performance penalty when it is enabled? (not all of DEBUG, just enabling this one feature of DEBUG)