All,
I have received this error message while running my code. I am using all STL code. I have also received stackdumps because of memory corruption.
Code:
*** glibc detected *** corrupted double-linked list:
I am dealing with a memory leak. I launch several threads, but never tear them down or relaunch them.
I have 32 test cases that I can run and reiterate the same testcase at least 3 times in the same operational session. I can execute them some where between 3-7 times before it crashes.
I have increased the thread stack size and found that it has helped increase the number of testcases that can be ran. If I run the code off of an 8GB USB stick (attached to the AT91 Board), it can seemingly execute forever and never receive a crash.
Unfortunately I can't see which thread is crashing and I'm working on getting some better eyes on the board. If anyone can recommend a program for an Angstrom build to see threads let me know.
I was hoping that someone can give me some ideas on what to look for when dealing with memory corruption. I'm pretty sure the program is stepping on its own memory which causes the crash.
Regards,
Mike