> I can't stop the gdb useing ctrl-c.
> Is there any need to "si" ? If so, this is a bug of valgrind, they should
> make sure of the assembly code is right.
At this moment, it is not clear what is wrong. It might be a bug or limitation
in Valgrind, it might
be something in your program.
> "a run under valgrind using a gdb on the native run" you mean" gdb --args
> valgrind [args]" ?
The idea is to compare an execution of your program directly under gdb
with an execution under Valgrind, with a gdb connected to the Valgrind
gdbserver.
You start valgrind the following way:
valgrind --vgdb=full --vgdb-error=0 ... your program ...
In another window, you start gdb:
gdb ... your program ...
... here you use target remote | vgdb to connect to valgrind gdbserver
.... you put breakpoints at the relevant places
.... you use the gdb continue command,
... and then you use 'si'
In 3rd window, you start your program under gdb
gdb ... your program ...
... put the same breakpoints as above
run and then in parallel use 'si' here and in the other gdb.
You can then compare what a native run is doing and what Valgrind is doing.
Philippe
------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
