Difference between revisions of "Pretty Printers"
From Code::Blocks
GravityWe11 (talk | contribs) |
GravityWe11 (talk | contribs) |
||
Line 8: | Line 8: | ||
<blockquote><span style="font-size: 10pt"><pre> | <blockquote><span style="font-size: 10pt"><pre> | ||
python | python | ||
− | import | + | import sys |
− | + | sys.path.insert(0, 'c:/MinGW/share/gcc-4.7.2/python/libstdcxx/v6') | |
− | |||
− | |||
from printers import register_libstdcxx_printers | from printers import register_libstdcxx_printers | ||
register_libstdcxx_printers (None) | register_libstdcxx_printers (None) |
Revision as of 21:25, 26 October 2012
GDB Pretty Printers for STL display nicely formatted variables in the hover pop-up and watch window, for all STL containers (vectors, maps, etc).
Test with GDB
- Install a python-enabled GDB. For Windows, you can install MinGW-Builds over MinGW (consider backing up MinGW first). This updates GCC to 4.7.2 and includes a Python enabled GDB.
- Create a GDB Command File to enable the printer. Store in c:\mingw\bin\pp.gdb (or wherever you want). Below is a sample command file. Replace the path c:/MinGW/share... with your path to printers.py. NOTE: A Python STL printer.py is included with MinGW and MinGW-Builds, so there is no need to download one. It only needs to be loaded into GDB's python, which is the purpose of the command file
python import sys sys.path.insert(0, 'c:/MinGW/share/gcc-4.7.2/python/libstdcxx/v6') from printers import register_libstdcxx_printers register_libstdcxx_printers (None) end
- Test
- Set a breakpoint in a program and debug
- Run the command file from GDB (can use Codeblocks->debugger tab->command, or in GDB from the console) (substitute your path if necessary)
(gdb) source c:\MinGW\bin\pp.gdb
- Test the printer - example:
(gdb) print words2 $1 = std::vector of length 3, capacity 4 = {"one", "two", "three"}
Add to Codeblocks
Once the command file is correctly loading the python printer into GDB, there are two steps to activate in Codeblocks:
- Set debugger initialization command:
Codeblocks->Settings->Debugger->Default->Debugger initialization commands
source $(TARGET_COMPILER_DIR)bin\pp.gdb
- Disable Codeblocks handling of watch values:
- Codeblocks->Settings->Debugger->Default->Enable Watch Scripts = Unchecked
Other Info
Links:
To Do
The third column in the Codeblocks popup and watch window displays a long unformatted string. Codeblocks is calling the GDB whatis command. Can this command be Pretty-Printed?