I'm using the Development Kit with NET+OS and am having trouble with my application. I would like some more information on the status of my threads as they execute.
You can load a simple gdb Threadx debugging script that will give some basic information about threads running in the application. From this you can determine the threads state, number of times it's been called, start and end addresses of its stack, and current location of the stack pointer.
This procedure assumes that you are using the command line GDB debugger instead of graphical GDBTK.
// This procedure explains how to print out a thread list during execution. This is intended for debugging purposes
copy gdbThreadx file into the applications 32b directory
open OCDLib Remote
from cygwin shell, go to applications 32b directory
launch gdb image.elf
From the GDB Debugger type:
Then, after the application starts you can then break into it and view the status of the threads with the following commands:
ctrl-C (allows to breakin)
threadlist (prints out thread information)