ansaurus

Question

Answer 1

+3 A:

in the gdb:

source {full_path}stl-views-1.0.3.gdb

now you'll have new commands, such as pvector, plist, pmap and more (replace {full_path} with the full path to the file.

You can also put the command source stl-views-1.0.3.gdb in ~/.gdbinit - and then you'll have it automatically every time you launch gdb.

Drakosha 2010-03-17 14:55:58

Do I have to do it every time I load gdb? Can it be done by default? Shuold stl-views-1.0.3.gdb be located in the current working directory?

vehomzzz 2010-03-17 14:58:11

Can't you just put it in your `~/.gdbinit`?

Jefromi 2010-03-17 15:02:02

Can you elaborate? So I start gdb and I type that? I just get `No such file or directory.`

Kache4 2010-03-17 15:22:07

@Kache4 do you actually have the file? source stl-views-1.0.3.gdb is NOT a command, but rather a command followed by the file name, although you've probably figured this out by now.

vehomzzz 2010-03-17 15:43:40

@Andrei: I guess not. `locate` doesn't find anything. Where can I get it? Quick Google search and search using Ubuntu synaptic didn't get me anything.

Kache4 2010-03-17 17:33:49

@Kache4: there's a link in the question itself

Drakosha 2010-03-17 19:48:37

I agree with "Employed Russian". This is the old - pre gdb7 - way of doing things. See the related http://stackoverflow.com/questions/2492020/how-to-view-contents-of-stl-containers-using-gdb-7-x

nimrodm 2010-06-29 18:37:23

Answer 2

+2 A:

As far as I can tell, stl-views are the old way to examine STL containers, and are inferior to the new python support in almost every way.

You should use libstdcxx_printers python pretty-printers instead.

Employed Russian 2010-03-18 06:21:33

Answer 3

A:

FYI, these instructions dont work on Ubuntu lucid at least. See this bug i just filed

kert 2010-06-29 18:27:36

ansaurus

tags:

views:

answers:

printing stl containers with gdb 7.0

related questions