Hi Everyone,
I've got a situation, where I need to find out why one of the several
dozend passes to that place leaks in the afterwards processing.
I learned about vgdb (whew, what a cool tool!) in the brand new 3.7
release, which probably would be the best way to achieve this;
Though i've still got a missing link: I need to get to know the pointers
to the memory which is leaked.
is there a way to add the pointers to the output of
monitor leak_check full reachable any
?
Next, an Issues I've found while playing around with vgdb in emacs GUD mode:
"monitor leak_check full reachable any" produces a lot of output;
it seems as if that somewhen breaks the connection;
I got "Remote connection closed"
then the Valgrind process blocks at that place, once one re-attaches it using
'target remote | vgdb'
it dumps the rest of the memory backtraces into its console; the Binary seems
to destabilize, I get:
relaying data between gdb and process 26736
Ignoring packet error, continuing...
warning: unrecognized item "timeout" in "qSupported" response
Ignoring packet error, continuing...
....
Malformed response to offset query, timeout
and then it terminates.
Cheers,
Wilfried Goesgens
------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create
new or port existing apps to sell to consumers worldwide. Explore the
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
