blocks|key|300352|text|我知道JDT+(eclipse中的Java环境)提供了在调试视图中显示变量值时要应用的自定义“格式化程序”。快速浏览一下google在CDT中的相同功能会显示以下页面：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|300353|http://wiki.eclipse.org/CDT/Better_Debugging_%2528GSoC_project%2529|offset|length|300354|我不知道这是否已经集成到CDT主行中了，也许你可以在调试时右击一个变量(在最后一个CDT中)，看看是否有一个自定义的格式表条目。如果不可用，我建议您在CDT跟踪器中添加一个新的跟踪器条目，以请求此增强。|300355|entityMap|0|LINK|mutability|MUTABLE|url|http://wiki.eclipse.org/CDT/Better_Debugging_%2528GSoC_project%2529^0|0|0|1R|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

I know that JDT (Java environment in eclipse) provides custom "formatters" to be applied when displaying variable values in debug views. A quick look at google for the same in CDT brings this page:

<a href="http://wiki.eclipse.org/CDT/Better_Debugging_%28GSoC_project%29" rel="nofollow noreferrer">http://wiki.eclipse.org/CDT/Better_Debugging_%28GSoC_project%29</a>

I don't know if this has been yet integrated in the main CDT line, may be you can try to right click on a variable while debugging (in the last CDT) and see if there is a custom formater entry. If not available I recomend you to add a new tracker entry in CDT tracker to ask this enhancement.

blocks|key|300381|text|好吧，gdb本身并不支持STL容器。你不能说这是不正确的，因为它会暴露STL对象的内部工作方式，但大多数时候这不是我们想要的，对吧？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|300382|如果你使用的是gdb+7.0，你可以利用漂亮的打印机。这个网站http://sourceware.org/gdb/wiki/STLSupport有一个关于如何设置它们的非常简单的教程。我复制了下面你感兴趣的部分：|offset|length|300383|300384|blockquote|300385|300386|300387|将最新的Python+libstdc%2B%2B打印机签出到您机器上的某个位置。在本地目录中，执行以下操作：|ordered-list-item|300388|300389|svn+co+svn://gcc.gnu.org/svn/gcc/trunk/libstdc%2B%2B-v3/python|300390|Add以下内容到您的~/.gdbinit。路径需要与上面的python模块的签出位置相匹配。因此，如果签出到:+/home/maude/gdb_printers/，则路径将如示例中所示：|unordered-list-item|300391|300392|python从libstdcxx.v6导入sys打印机(0，‘/home/maude/gdb_sys.path.insert/python’)。打印机导入register_libstdcxx_printers+register_libstdcxx_printers+(None)+end|300393|路径应该是上面示例中唯一需要调整的元素。加载后，打印机支持的STL类应以更易读的格式打印。要以旧样式打印类，请在打印命令中使用/r+(raw)开关(例如，print+/r+foo)。这将打印类，就像没有加载Python漂亮打印机一样。|300394|由于您使用的是eclipse+cdt，所以不要忘记将调试配置指向.gdbinit文件。在创建新的调试配置时，转到Debugger选项卡，并将.gdbinit文件的路径放在"GDB+command+file“字段中。|300395|我希望这对你有帮助！|300396|entityMap|0|LINK|mutability|MUTABLE|url|http://sourceware.org/gdb/wiki/STLSupport^0|0|V|15|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1B|8|@]|9|@$D|1C|E|1D|1|1E]]|A|$]]|$1|F|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]|$1|G|3|-4|5|H|7|1G|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]|$1|K|3|L|5|M|7|1J|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1L|8|@]|9|@]|A|$]]|$1|Q|3|R|5|S|7|1M|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1N|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1O|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1P|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|1R|8|@]|9|@]|A|$]]|$1|12|3|-4|5|6|7|1S|8|@]|9|@]|A|$]]]|13|$14|$5|15|16|17|A|$18|19]]]]

Well, gdb don't natively support STL containers. You can't say this is incorrect, since it will expose the inner workings of the STL objects, but most of the time it is not what we want, right?

If you're using gdb 7.0 you can take advantage of the pretty printers. This website <a href="http://sourceware.org/gdb/wiki/STLSupport" rel="noreferrer">http://sourceware.org/gdb/wiki/STLSupport</a> has a pretty simple tutorial on how to set them. I copied below the part that interests you:

<blockquote>
 <ol>
 <li>Check-out the latest Python libstdc++ printers to a place on your
 machine. In a local directory, do:

<pre><code> svn co svn://gcc.gnu.org/svn/gcc/trunk/libstdc++-v3/python
</code></pre></li>
 <li>Add the following to your ~/.gdbinit. The path needs to match
 where the python module above was
 checked-out. So if checked out to:
 /home/maude/gdb_printers/, the path
 would be as written in the example:

<pre><code> python
 import sys
 sys.path.insert(0, '/home/maude/gdb_printers/python')
 from libstdcxx.v6.printers import register_libstdcxx_printers
 register_libstdcxx_printers (None)
 end
</code></pre></li>
 </ol>
 
 The path should be the only element
 that needs to be adjusted in the
 example above. Once loaded, STL
 classes that the printers support
 should printed in a more
 human-readable format. To print the
 classes in the old style, use the /r
 (raw) switch in the print command
 (i.e., print /r foo). This will print
 the classes as if the Python
 pretty-printers were not loaded.
</blockquote>

Since you're using eclipse cdt, don't forget to point your debug configuration to your .gdbinit file. When creating a new Debug Configuration, go to the Debugger tab and put the path to the .gdbinit file in the "GDB command file" field.

I hope that helps!

blocks|key|3023882|text|您需要一个能够使用python来美化打印结构的GDB版本。我知道，至少在使用mingw的windows上，默认安装中不提供此功能。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3023883|漂亮的打印机是python模块，它告诉gdb如何显示给定的结构。您可以编写自己的打印机，但已经有STL打印机可供下载。|3023884|要让漂亮的打印机在Windows上运行(说明应该与其他操作系统类似)：|3023885|前提条件|offset|length|style|BOLD|3023886|3023887|确保在系统路径中安装了Python2.7。|unordered-list-item|3023888|3023889|http://www.python.org/download/|3023890|3023891|确保安装了MinGW-get|3023892|3023893|http://sourceforge.net/projects/mingw/files/Installer/mingw-get-inst/|3023894|3023895|确保已安装SVN客户端|3023896|3023897|Installation:|3023898|3023899|打开命令外壳并键入：|3023900|3023901|mingw-get通过键入以下命令，将gdb-python|3023902|When及其完成的cd安装到本地目录并安装打印机：|3023903|3023904|svn+co+svn://gcc.gnu.org/svn/gcc/trunk/libstdc%2B%2B-v3/python|3023905|Open该目录(如果需要，请在文本编辑器中创建它)，然后键入以下内容，将“C:/+.gdbinit”替换为您将打印机检入到的文件夹。|3023906|3023907|Python|3023908|导入sys|3023909|sys.path.insert(0，‘C:/目录’)|3023910|从libstdcxx.v6导入register_libstdcxx_printers|3023911|register_libstdcxx_printers+(无)|3023912|结束|3023913|Eclipse设置|3023914|3023915|转到窗口>首选项>+C/C%2B%2B+>调试>+GDB+|3023916|，其中显示GDB调试器将路径放置到启用了python的GDB，它很可能位于名为gdb-python27.exe|3023917|Where的/bin文件夹中。它显示GDB命令文件将您先前创建的.gdb初始化文件的路径放入其中。|3023918|3023919|就是这样，像正常一样调试，stl结构应该更容易阅读。|3023920|entityMap|0|LINK|mutability|MUTABLE|url|1^0|0|0|0|0|4|0|0|0|0|0|V|0|0|0|0|0|0|1X|1|0|0|0|0|0|D|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|9|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|2E|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|2F|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|2G|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|2H|8|@$H|2I|I|2J|J|K]]|9|@]|A|$]]|$1|L|3|-4|5|6|7|2K|8|@]|9|@]|A|$]]|$1|M|3|N|5|O|7|2L|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|2M|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|2N|8|@]|9|@$H|2O|I|2P|1|2Q]]|A|$]]|$1|S|3|-4|5|6|7|2R|8|@]|9|@]|A|$]]|$1|T|3|U|5|O|7|2S|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|2T|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|2U|8|@]|9|@$H|2V|I|2W|1|2X]]|A|$]]|$1|Y|3|-4|5|6|7|2Y|8|@]|9|@]|A|$]]|$1|Z|3|10|5|O|7|2Z|8|@]|9|@]|A|$]]|$1|11|3|-4|5|6|7|30|8|@]|9|@]|A|$]]|$1|12|3|13|5|6|7|31|8|@$H|32|I|33|J|K]]|9|@]|A|$]]|$1|14|3|-4|5|6|7|34|8|@]|9|@]|A|$]]|$1|15|3|16|5|O|7|35|8|@]|9|@]|A|$]]|$1|17|3|-4|5|6|7|36|8|@]|9|@]|A|$]]|$1|18|3|19|5|6|7|37|8|@]|9|@]|A|$]]|$1|1A|3|1B|5|O|7|38|8|@]|9|@]|A|$]]|$1|1C|3|-4|5|6|7|39|8|@]|9|@]|A|$]]|$1|1D|3|1E|5|6|7|3A|8|@]|9|@]|A|$]]|$1|1F|3|1G|5|O|7|3B|8|@]|9|@]|A|$]]|$1|1H|3|-4|5|6|7|3C|8|@]|9|@]|A|$]]|$1|1I|3|1J|5|6|7|3D|8|@]|9|@]|A|$]]|$1|1K|3|1L|5|6|7|3E|8|@]|9|@]|A|$]]|$1|1M|3|1N|5|6|7|3F|8|@]|9|@]|A|$]]|$1|1O|3|1P|5|6|7|3G|8|@]|9|@]|A|$]]|$1|1Q|3|1R|5|6|7|3H|8|@]|9|@]|A|$]]|$1|1S|3|1T|5|6|7|3I|8|@]|9|@]|A|$]]|$1|1U|3|1V|5|6|7|3J|8|@$H|3K|I|3L|J|K]]|9|@]|A|$]]|$1|1W|3|-4|5|6|7|3M|8|@]|9|@]|A|$]]|$1|1X|3|1Y|5|O|7|3N|8|@]|9|@]|A|$]]|$1|1Z|3|20|5|O|7|3O|8|@]|9|@]|A|$]]|$1|21|3|22|5|O|7|3P|8|@]|9|@]|A|$]]|$1|23|3|-4|5|6|7|3Q|8|@]|9|@]|A|$]]|$1|24|3|25|5|6|7|3R|8|@]|9|@]|A|$]]|$1|26|3|-4|5|6|7|3S|8|@]|9|@]|A|$]]]|27|$28|$5|29|2A|2B|A|$2C|R]]|2D|$5|29|2A|2B|A|$2C|X]]]]

You need a version of GDB capable of using python to pretty print structures. I know at least on windows using mingw that this is not provided in the default install.

Pretty Printers are python modules which tell gdb how to display a given structure. You can write your own, but there are already printers for STL available for download. 

To Get Pretty Printers working on Windows (instructions should be similiar for other OS's):

Prerequisites

<ul>
<li>Make sure you have you have Python 2.7 installed and in the system path.

<blockquote>
 <a href="http://www.python.org/download/" rel="noreferrer">http://www.python.org/download/</a>
</blockquote></li>
<li>Make sure MinGW-get is installed

<blockquote>
 <a href="http://sourceforge.net/projects/mingw/files/Installer/mingw-get-inst/" rel="noreferrer">http://sourceforge.net/projects/mingw/files/Installer/mingw-get-inst/</a>
</blockquote></li>
<li>Make sure you have an SVN client are installed</li>
</ul>

Installation:

<ul>
<li>Open a command Shell and type:

<pre><code>mingw-get install gdb-python
</code></pre></li>
<li>When its finished cd to a local directory and install the printers by typing:

<pre><code>svn co svn://gcc.gnu.org/svn/gcc/trunk/libstdc++-v3/python
</code></pre></li>
<li>Open the .gdbinit (create it in a text editor if need be) and type the following replaceing "C:/directory" with the folder that you checked the printers into.

<blockquote>
 Python 
 import sys 
 sys.path.insert(0, 'C:/directory') 
 from libstdcxx.v6.printers import register_libstdcxx_printers 
 register_libstdcxx_printers (None) 
 end 
</blockquote></li>
</ul>

Eclipse Setup

<ul>
<li>Go To Windows > Preferences > C/C++ > Debug > GDB</li>
<li>Where it Says GDB Debugger put the path to the python enabled GDB it will most likely be in the mingw /bin folder with a name like gdb-python27.exe</li>
<li>Where it says GDB Command File put the path to the .gdb init file you made earlier.</li>
</ul>

That's it, debug like normal, the stl structures should be much easier to read.

blocks|key|300429|text|如果您具有对CDT的gdb支持(例如，请参见GDB+in+Eclipse)，您可以尝试这样做：De-referencing+STL+containers|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|300430|很久以前，我也偶然发现了你同样的问题。检查STL容器是一件痛苦的事情。然后，我找到了这个链接，并将其中一些定义添加到我的.gdbinit文件中。在那之后，生活变得更容易了。|300431|注意：我的gdb版本是7.1，添加这些定义可以很好地工作。我不知道在较新版本的gdb中是否已经包含了它们。|BOLD|300432|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/3758794/how-do-i-use-gdb-in-eclipse-for-c-c-debugging|1|http://www.yolinux.com/TUTORIALS/GDB-Commands.html#STLDEREFhttp://www.yolinux.com/TUTORIALS/GDB-Commands.html#STLDEREF^0|6|3|A|3|M|E|0|1B|T|1|0|1O|8|0|0|3|5|3|13|3|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]]|D|@$9|Z|A|10|1|11]|$9|12|A|13|1|14]]|E|$]]|$1|F|3|G|5|6|7|15|8|@$9|16|A|17|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|18|8|@$9|19|A|1A|B|J]|$9|1B|A|1C|B|C]|$9|1D|A|1E|B|C]]|D|@]|E|$]]|$1|K|3|-4|5|6|7|1F|8|@]|D|@]|E|$]]]|L|$M|$5|N|O|P|E|$Q|R]]|S|$5|N|O|P|E|$Q|T]]]]

If you have <code>gdb</code> support for <code>CDT</code> (see, for example, <a href="https://stackoverflow.com/questions/3758794/how-do-i-use-gdb-in-eclipse-for-c-c-debugging">GDB in Eclipse</a>), you could try this: <a href="http://www.yolinux.com/TUTORIALS/GDB-Commands.html#STLDEREFhttp://www.yolinux.com/TUTORIALS/GDB-Commands.html#STLDEREF" rel="nofollow noreferrer">De-referencing STL containers</a>

Long ago I also stumbled upon your same problem. It was a pain to check the STL containers. Then I found that link and added to my <code>.gdbinit</code> file some of those definitions. Life was easier after that.

NOTE: My <code>gdb</code> version is 7.1 and adding those definitions work fine. I don't know if in newer versions of <code>gdb</code> they are already included.

blocks|key|3024016|text|我想详述Windows+7的回应，因为一些关键步骤被省略了：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3024017|本文适用于使用Eclipse+CDT的MinGW用户|3024018|0)如果你没有python+GDB，打开一个shell/命令并使用MinGW-get.exe来‘安装’支持Python的GDB。|3024019|+++MinGw-get.exe+install+gdb-python|code-block|syntax|javascript|3024020|1a)从http://python.org/download/获取Python2.7.x并安装|offset|length|3024021|1b)确保在您的环境中设置了PYTHONPATH和PYTHONHOME：|3024022|+PYTHONPATH+should+be+C:\Python27\Lib+++(or+similar)
+PYTHONHOME+should+be+C:\Python27|3024023|1c)将PYTHONHOME添加到您的路径中|3024024|+%25PYTHONHOME%25;...|3024025|2a)打开文本回车，输入以下语句。请注意，第三行指向python脚本所在的位置。请看下面关于这方面的说明！|3024026|python
import+sys
sys.path.insert(0,+'C:/MinGW/share/gcc-4.6.1/python')+++++++++
from+libstdcxx.v6.printers+import+register_libstdcxx_printers
register_libstdcxx_printers+(None)
end|3024027|2b)另存为'.gdbinit‘注意:+Windows资源管理器不允许您从资源管理器中命名以句点开头的文件。大多数文本编辑(包括记事本)将允许您。GDB+init文件类似于GDB命令的“脚本”，GBD将在加载时执行这些脚本。|3024028|2c)+'.gdbinit‘文件需要在GDB的工作目录中(这很可能是你的项目的根目录，但是你的集成开发环境可以告诉你。|3024029|3)打开Eclipse+(或其他IDE)首选项对话框。转到C%2B%2B调试器子菜单。|3024030|4)将Eclipse配置为使用C:\MinGW\bin\gdb-python27.exe作为调试器，使用.gdbinit作为配置文件。|style|CODE|3024031|5a)重新创建所有调试启动配置(删除旧配置并从头创建一个新配置)。|3024032|--OR--|3024033|5b)编辑每个调试配置并将其指向新的gdb-python.exe，然后将其指向。|3024034|如果您遇到问题：|3024035|--不要忘记在上面的python代码中将位置更改为python目录！这个目录是由MinGW创建的，所以不要去下载漂亮的打印机，MinGW在步骤0中已经为您完成了。只要进入你的MinGW安装目录，共享文件夹，GCC文件夹(有版本号)，你就会找到python文件夹。这个位置应该在GDB加载的python脚本中。|3024036|--此外，.gdbinit是一个PITA，请确保它的名称正确，并且位于GDB的工作文件夹中，而gdb-python.exe不一定位于该文件夹中！在加载GDB时查看GDB的输出，看看在加载过程中是否出现了'python-enabled‘，以及.gdbinit中的语句是否出现。|3024037|--最后，我在系统变量方面遇到了很多问题。如果python给了你'ImportError‘，那么很可能你没有设置PYTHONPATH或PYTHONHOME。|3024038|--带有'gdb-python27‘的目录(例如C:\MinGW\bin')也应该在你的path中，如果它在你的path中，它会使eclipse的设置变得更好，因为你不需要放入绝对路径。但是，有时.gbdinit仍然需要一条非正式的路径。如果它工作正常，你会在启动调试器时看到gbd+(控制台->gdb跟踪)的输出：|3024039|835,059+4%5Edone
835,059+(gdb)+
835,059+5-enable-pretty-printing
835,069+5%5Edone
....
835,129+12%5Edone
835,129+(gdb)+
835,129+13source+C:\MinGW\bin\.gdbinit
835,139+&"source+C:\\MinGW\\bin\\.gdbinit\n"
835,142+13%5Edone
835,142+(gdb)+|3024040|entityMap|0|LINK|mutability|MUTABLE|url|http://python.org/download/^0|0|0|0|0|4|R|0|0|0|0|0|0|0|0|0|0|0|F|T|1G|8|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|20|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|21|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|22|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|23|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|24|8|@]|9|@$M|25|N|26|1|27]]|A|$]]|$1|O|3|P|5|6|7|28|8|@]|9|@]|A|$]]|$1|Q|3|R|5|H|7|29|8|@]|9|@]|A|$I|J]]|$1|S|3|T|5|6|7|2A|8|@]|9|@]|A|$]]|$1|U|3|V|5|H|7|2B|8|@]|9|@]|A|$I|J]]|$1|W|3|X|5|6|7|2C|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|H|7|2D|8|@]|9|@]|A|$I|J]]|$1|10|3|11|5|6|7|2E|8|@]|9|@]|A|$]]|$1|12|3|13|5|6|7|2F|8|@]|9|@]|A|$]]|$1|14|3|15|5|6|7|2G|8|@]|9|@]|A|$]]|$1|16|3|17|5|6|7|2H|8|@$M|2I|N|2J|18|19]|$M|2K|N|2L|18|19]]|9|@]|A|$]]|$1|1A|3|1B|5|6|7|2M|8|@]|9|@]|A|$]]|$1|1C|3|1D|5|H|7|2N|8|@]|9|@]|A|$I|J]]|$1|1E|3|1F|5|6|7|2O|8|@]|9|@]|A|$]]|$1|1G|3|1H|5|6|7|2P|8|@]|9|@]|A|$]]|$1|1I|3|1J|5|6|7|2Q|8|@]|9|@]|A|$]]|$1|1K|3|1L|5|6|7|2R|8|@]|9|@]|A|$]]|$1|1M|3|1N|5|6|7|2S|8|@]|9|@]|A|$]]|$1|1O|3|1P|5|6|7|2T|8|@]|9|@]|A|$]]|$1|1Q|3|1R|5|H|7|2U|8|@]|9|@]|A|$I|J]]|$1|1S|3|-4|5|6|7|2V|8|@]|9|@]|A|$]]]|1T|$1U|$5|1V|1W|1X|A|$1Y|1Z]]]]

I would like to expand on the Windows 7 response because some key steps are left out:

<h1>This is for MinGW users with Eclipse CDT</h1>

0) If you don't have python GDB, open a shell/command and use MinGW-get.exe to 'install' 
 Python-enabled GDB e.g. 

<pre><code> MinGw-get.exe install gdb-python
</code></pre>

1a) Get Python 2.7.x from <a href="http://python.org/download/" rel="noreferrer">http://python.org/download/</a> and install

1b) Make sure PYTHONPATH and PYTHONHOME are set in your environment:

<pre><code> PYTHONPATH should be C:\Python27\Lib (or similar)
 PYTHONHOME should be C:\Python27
</code></pre>

1c) Add PYTHONHOME to your PATH

<pre><code> %PYTHONHOME%;...
</code></pre>

2a) Open a text enter, enter the following statements. Notice the 3rd line is
 pointing to where the python scripts are located. See notes below about this!

<pre><code>python
import sys
sys.path.insert(0, 'C:/MinGW/share/gcc-4.6.1/python') 
from libstdcxx.v6.printers import register_libstdcxx_printers
register_libstdcxx_printers (None)
end
</code></pre>

2b) Save as '.gdbinit' NOTE: Windows explorer will not let you name a file that starts with
 with a period from explorer. Most text edits (including Notepad) will let you. GDB init
 files are like 'scripts' of GDB commands that GBD will execute upon loading. 

2c) The '.gdbinit' file needs to be in the working directory of GDB (most likely this is
 your projects root directory but your IDE can tell you.

3) Open your Eclipse (or other IDE) Preferences dialog. Go to the C++ Debugger sub-menu.

4) Configure Eclipse to use <code>C:\MinGW\bin\gdb-python27.exe</code> as the debugger and your <code>.gdbinit</code> as the config file. 

5a) Re-create all your debug launch configurations (delete the old one and create a new one from scratch).

<pre><code>--OR--
</code></pre>

5b) Edit each debug configuration and point it to the new gdb-python.exe AND point it to the.

<h2>If you run into issues:</h2>

--Don't forget to change the location to the python directory in the above python code!
 This directory is created by MinGW, so don't go looking to download the pretty printers, MinGW
 did it for you in step zero. Just goto your MinGW install director, the share folder,
 the GCC folder (has version number) and you will find python folder. This location is what
 should be in python script loaded by GDB.

--Also, the .gdbinit is a PITA, make sure its named correctly and in the working folder of GDB 
 which isn't necessarily where gdb-python.exe is located! Look at your GDB output when loading GDB to see if a) 'python-enabled' appears during load and that the statements in the .gdbinit are appearing.

--Finally, I had alot of issues with the system variables. If python gives you 'ImportError' then most likely you have not set PYTHONPATH or PYTHONHOME. 

--The directory with 'gdb-python27' (e.g. C:\MinGW\bin') should also be on your path and if it is, it makes setting up eclipse a bit nicer because you don't need to put in absolute paths. But still, sometimes the .gbdinit needs an absoulte path. if it works you'll see output from gbd (console->gdb traces) like this on startup of debugger:

<pre><code>835,059 4^done
835,059 (gdb) 
835,059 5-enable-pretty-printing
835,069 5^done
....
835,129 12^done
835,129 (gdb) 
835,129 13source C:\MinGW\bin\.gdbinit
835,139 &amp;"source C:\\MinGW\\bin\\.gdbinit\n"
835,142 13^done
835,142 (gdb) 
</code></pre>

blocks|key|297861|text|在调试视图的变量列表中展开向量：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|297862|"vector_name"+->+std::_Vector_base<"datatype">+->+_M_impl|offset|length|style|CODE|297863|然后右键单击_M_start并选择“显示为数组...”，键入其长度，然后单击确定。现在，您可以展开向量的每一项。|297864|entityMap^0|0|0|D|H|T|1E|7|0|6|8|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]|$D|P|E|Q|F|G]|$D|R|E|S|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@$D|U|E|V|F|G]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|K|$]]

In debug view in variables list expand vector:

<code>"vector_name"</code> -> <code>std::_Vector_base&lt;"datatype"&gt;</code> -> <code>_M_impl</code>

then right click on <code>_M_start</code> and select "Display as array...", type its length and then click OK. Now you can expand each item of your vector.

Using Eclipse and CDT to debug C++ code the variable windows is cumbersome and not very informative for types defined in the standard template library or in boost (e.g. shared_ptr).
Just an example how this may look like for an std::vector:
<pre><code>bar {…}
 std::_Vector_base&lt;TSample&lt;MyTraits&gt;, std::allocator&lt;TSample&lt;MyTraits&gt; &gt; &gt; 
 _M_impl {…} 
 std::allocator&lt;TSample&lt;MyTraits&gt; &gt; {…} 
 _M_start 0x00007ffff7fb5010 
 _M_finish 0x00007ffff7fd4410 
 _M_end_of_storage 0x00007ffff7fd5010 
</code></pre>
Even if this information about the internals of those types may be useful, in almost any cases I would expect a clearer presentation here, i.e. a list of values for the std::vector. Are there any tools, plugins or other modifications around which can do this?
EDIT
The following solutions does not work for linux. I am using ubuntu 14.04, eclipse, g++, gdb.
I cant find a package gdb-python and linux does not use mingw

Better variable exploring when debugging C++ code with Eclipse/CDT

集成开发环境

调试器

Windows

Eclipse

容器

Python

Java

使用Eclipse和CDT调试C++代码的变量窗口很麻烦，而且对于在标准模板库或boost (例如shared_ptr)中定义的类型来说，信息不是很丰富。这只是一个std：：vector的示例：bar {…} std::_Vector_base<TSample<MyTraits>, std::allocator<...

问在使用Eclipse/CDT调试C++代码时更好地探索变量
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在使用Eclipse/CDT调试C++代码时更好地探索变量EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在使用Eclipse/CDT调试C++代码时更好地探索变量
EN