std::vector in the debugger: i don't understand the previous topic

[21did21]

Hello world,

i am new in programmation (and in code::block); when i debugg, i want to see the contents of the vectors.
I have seen that in this forum there is already one subject ( http://forums.codeblocks.org/index.php/topic,10667.msg73032.html#msg73032 )
but i don't understand it, because:
- my english is poor and in this subject the number of developpement are very long and i don't understand that is important.

Can you resume please for me the different step to can see the content of vector<double> , vector<int>, vector<string> ...
thanks a lot!

ps: in debugg mode, I do not know how to look at the contents of variables: i clikck right on variable and i do :

watch"myVariable"

and in the debugg windows i obtain this: MyVariable=No symbol "myVariable" in current context

[ollydbg]

I suggest you can use a python supported gdb.
If you use windows, see:
http://code.google.com/p/qp-gcc/wiki/GDB

[21did21]

I suggest you can use a python supported gdb.
If you use windows, see:
http://code.google.com/p/qp-gcc/wiki/GDB

thank a lot for your help!
i have download the package and i have configurated this step:"Load the python script when Debugger started in Codeblocks" of your page
but after this i always can't see the content of my variables and my vector, other step are necessary?

==> (my english is bad end i am a little beginniner in programmation, this is the reason that it don't understand all)


EDIT:
-for a very simple it's work for double end int type, but it don't work for vector?
-for values close to 0 the debugg show 0 end not 1e-20 !!! it's normal ?

[21did21]

it's work now!!! thank you a lot !!!

just one think:
==> we can't see the content of:  vector <vector <double>> ?

[oBFusCATed]

if you use the python pretty printing you can.

To disable the C::B pretty printing you should comment the code inside RegisterTypes in the file gdb_types.script.

[21did21]

if you use the python pretty printing you can.
To disable the C::B pretty printing you should comment the code inside RegisterTypes in the file gdb_types.script.

sorry I'm not good in what file should I do what you say?
(see attached item)

[oBFusCATed]

Why don't you use the search function of your Explorer?  :lol:

[21did21]

Why don't you use the search function of your Explorer?  :lol:

 :oops: excuse me I had not thought   :oops:
( it is here:  E:\Program Files\CodeBlocks\share\CodeBlocks\scripts )

But that line i have to modify? i have put in comment all the function " function RegisterTypes(driver) " but my problem is not solve....  :shock:

[oBFusCATed]

Hm, my mistake the python pretty printers are broken, too.

Edit: after more testing it seems to work, partly, but the parser is broken. I'm testing with the debugger's branch. Probably 10.05 is even more broken.

[21did21]

Hm, my mistake the python pretty printers are broken, too.
Edit: after more testing it seems to work, partly, but the parser is broken. I'm testing with the debugger's branch. Probably 10.05 is even more broken.

oK? Thank you for your help. if you find the solution please let me informed

[oBFusCATed]

Can you enable the debugger's debug log and paste the output of your debug session?

To enable the log go to Settings -> Compiler & Debugger -> Display debugger's log.

p.s. please use code tags

[21did21]

Can you enable the debugger's debug log and paste the output of your debug session?
To enable the log go to Settings -> Compiler & Debugger -> Display debugger's log.
p.s. please use code tags

thank you for your help, this is the output of my debugg:

Code

Building to ensure sources are up-to-date
Build succeeded
Selecting target: 
Debug
Adding source dir: D:\myProgram\
Adding source dir: D:\myProgram\
Adding file: bin\Debug\myProgram.exe
Starting debugger: 
done
Registered new type: wxString
Registered new type: STL String
Registered new type: STL Vector
Setting breakpoints
Debugger name and version: GNU gdb (GDB) 7.2
Child process PID: 5680
Program exited normally.
Debugger finished with status 0

[oBFusCATed]

No, it is not.

Code

Registered new type: wxString
Registered new type: STL String
Registered new type: STL Vector

Looks like you've not disabled the pretty printers inside C::B!

[21did21]

No, it is not.

Code

Registered new type: wxString
Registered new type: STL String
Registered new type: STL Vector

Looks like you've not disabled the pretty printers inside C::B!

thank you for your help, what is "pretty printers"?
in attached item you have my result (it work for a vector but not for a vector <vector > double > )
and you have my configuration.

[oBFusCATed]

Pritty printers are pieces of code which transform the ugly output of gdb in something readable. They hide the implementation details of a vector for example and transform it into something looking like array.

The vector<vector<double>> doesn't work because you have not correctly commented out the function RegisterTypes(driver) function.