Btw, as Phillip asked...
I'm doing an event driven Program (using libev), in which some contexts
failed, and lost their memory.
I've added my pointers to the logging, plus some more logging which contexts
cleaned up properly,
but a list of the pointers still reachable infront of the backtraces would
have been the quick way to look into this memory and find out which contexts
(with mails to which recipients in that case)
Valgrind would have saved me the sort/grep/... work to filter out the free'd
and the unfreed contexts and about a day of handwork.
(over the hundrets of years valgrind saves me by aiding me in bug & memleak
search every day ;-)
> Fri Dec 23 2011 12:52:22 EST from "Wilfried Goesgens"
><dotheb...@citadel.org> Subject: [Valgrind-users] exploring the memory of a
>leak report?
>
>
>
>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
>
> (, 0 bytes) [View| Download]
>
>
>
>
> (, 0 bytes) [View| Download]
>
>
>
>
>
>
>
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
------------------------------------------------------------------------------
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
------------------------------------------------------------------------------
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
