User forums > Using Code::Blocks
see content of a vector in debugging
ollydbg:
--- Quote from: mandrav on June 15, 2009, 04:03:41 pm ---
--- Quote from: killerbot on June 15, 2009, 02:49:55 pm ---However the main question remains to the other developers : does anyone expect side effects.
--- End quote ---
It mostly depends on whether gdb init commands may have valid $something commands that should NOT be expanded by C::B...
--- End quote ---
We can have two edit controls. One for expanded, the other then directly passed to GDB :D
killerbot:
--- Quote from: mandrav on June 15, 2009, 04:03:41 pm ---
--- Quote from: killerbot on June 15, 2009, 02:49:55 pm ---However the main question remains to the other developers : does anyone expect side effects.
--- End quote ---
It mostly depends on whether gdb init commands may have valid $something commands that should NOT be expanded by C::B...
--- End quote ---
does anyone know of such commands ?
My knowledge of gdb is not that big, so because I don't know any is not good enough for a general conclusion ;-)
oBFusCATed:
source command might not support variable expansion at all:
http://sourceware.org/ml/gdb/2006-06/msg00092.html
Jenna:
--- Quote from: killerbot on June 15, 2009, 04:19:41 pm ---does anyone know of such commands ?
--- End quote ---
Quote from gdb documentation:
--- Quote from: gdb-docu ---You can use the string ‘$cdir’ to refer to the compilation directory (if one is
recorded), and ‘$cwd’ to refer to the current working directory. ‘$cwd’ is not
the same as ‘.’—the former tracks the current working directory as it changes
during your gdb session, while the latter is immediately expanded to the current
directory at the time you add an entry to the source path.
--- End quote ---
There seem to be some more:
--- Quote from: gdb documentation's index ---$ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
$$ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
$_ and info breakpoints . . . . . . . . . . . . . . . . . . . . 40
$_ and info line . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
$_, $__, and value history . . . . . . . . . . . . . . . . . . . . 81
$_, convenience variable . . . . . . . . . . . . . . . . . . . . . . 89
$__, convenience variable . . . . . . . . . . . . . . . . . . . . . 89
$_exitcode, convenience variable . . . . . . . . . . . . . 90
$bpnum, convenience variable . . . . . . . . . . . . . . . . . . 38
$cdir, convenience variable . . . . . . . . . . . . . . . . . . . 71
$cwd, convenience variable . . . . . . . . . . . . . . . . . . . . 71
$tpnum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
$trace_file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
$trace_frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
$trace_func . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
$trace_line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
$tracepoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
--- End quote ---
oBFusCATed:
Does that apply to the source command? Can you give a link for the excerpt from the gdb docs?
--- Code: ---(gdb) source $cwd/test.gdb
$cwd/test.gdb: No such file or directory.
--- End code ---
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version