Using PEEDI
A loop is successful only if the last NEXT pointer points to the start pointer. In this case PEEDI
reports to gdb all found threads.
When looping, if there is a NULL pointer or garbage read, then PEEDI will report only one thread -
the current execution.
To prevent garbage reading from uninitialized memory (for example after the first "si" command) it
is recommended gdbinit file to clear the first NEXT pointer.
Something like this:
set Cyg_Thread::thread_list->next=0
Start your project with GDB and observe the console. The script prints information in the form of a
configuration file OS section. Use the script only once to obtain the section. For example to print
the eCOS section enter ecos in the GDB console.
See an example GDB command window below:
PEEDI User’s Manual
102
