|
From: Wilfried G. <dot...@ci...> - 2011-12-23 18:40:22
|
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 |
|
From: Wilfried G. <dot...@ci...> - 2011-12-24 21:05:56
|
_______________________________________________ Valgrind-users mailing list Val...@li... https://lists.sourceforge.net/lists/listinfo/valgrind-users |
|
From: WAROQUIERS P. <phi...@eu...> - 2011-12-28 09:04:50
|
> 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 > ? I just attached a patch to https://bugs.kde.org/show_bug.cgi?id=289939 which implements the following two new memcheck gdbserver monitor commands: block_list <loss_record_nr> after a leak search, shows the list of blocks of <loss_record_nr> who_points_at <addr> [<len>] shows places pointing inside <len> (default 1) bytes at <addr> (with len 1, only shows "start pointers" pointing exactly to <addr>, with len > 1, will also show "interior pointers") Waiting for review/feedback/... about the above ... > I got "Remote connection closed" Fixed in 3.8.0 SVN (Revision: 12319). See bug https://bugs.kde.org/show_bug.cgi?id=289699 Philippe ____ This message and any files transmitted with it are legally privileged and intended for the sole use of the individual(s) or entity to whom they are addressed. If you are not the intended recipient, please notify the sender by reply and delete the message and any attachments from your system. Any unauthorised use or disclosure of the content of this message is strictly prohibited and may be unlawful. Nothing in this e-mail message amounts to a contractual or legal commitment on the part of EUROCONTROL, unless it is confirmed by appropriately signed hard copy. Any views expressed in this message are those of the sender. |