Are you proposing an universal, system-agnostic data format, which would allow to debug any RTOS which provides that data in OpenOCD?
I suppose it could be possible, but only for some RTOSes. The reason is that there are several different ways to "arrange" threads in the scheduler and in each case the code to handle that (and the needed data for OpenOCD would be different). Without much thinking, there are at least these three: - threads arranged in a single list meant for debug purposes only (your project, my project, ChibiOS/RT, ...), - threads arranged in multiple lists (state lists in FreeRTOS - the design of that thing constantly puzzles me...), - fixed size array. (I know of RTOSes which are actually doing more than one of these methods at once - things like that puzzle me quite often...) What you propose would work only for the first group, maybe with slight modifications with the second group too. To make that truly universal, you'd probably have to abstract the operation of "getting next task", which would be pretty hard to do in the struct only and would probably require some scripting support. But I bet there are more minor details that actually have important implications for such generic OpenOCD support. For example the thread name can be stored as an array (I think this approach is more popular) or a pointer only. Don't get me wrong - the idea is tempting, I just fear that if implemented it would work only for a fraction of available RTOSes (most likely the ones you had in mind when writing that and nothing more). Regards, FCh ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
