I would like to cut-paste the call stack, or local variable values, or watch-window values into a text file so that I can save the context of a particular debugging session for later discussion or reference.
Idea Originally Posted by: Paul Nguyen 01/12/2009
14/04/2011 Jonathan Elliott (Admin)
The CrossWorks V2 IDE has the command-line debugging window (Debug > Debug Windows > Debug Immediate). You could use this, I believe the command line is documented. However, it's easy enough to use debug I/O over the JTAG connection or write directly to files using debug I/O.
14/04/2011 Paul Nguyen
one way this is accomplished is to provide a window within the IDE that has a command interface. You type a command and the data is presented in text format. Of particular interest is the dumping of memory. The key part of this feature is that it allows the data to be portable. As mentioned, sometimes you want to capture data for later analysis. If you can't do this, your'e stuck with having to immediately analyze the data, or losing it because you don't have time immediately to do it.
Please sign in to leave a comment.