[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [valgrind] [Bug 371770] Memleak trace back for overwritten or freed memory pointers
From:       Joe Veazey <bugzilla_noreply () kde ! org>
Date:       2016-10-31 21:45:17
Message-ID: bug-371770-17878-x22oCehDWQ () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=371770

--- Comment #3 from Joe Veazey <joe.veazey@ipdatatel.com> ---
I will investigate your suggestions. gdb+vgdb w/breakpoints sounds the most
feasible for my task.

Thanks for the reply!

*Joe.Veazey@ipdatatel.com <Joe.Veazey@ipdatatel.com>*
Cell: 281-543-8330

On Mon, Oct 31, 2016 at 4:42 PM, Philippe Waroquiers <
bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=371770
>
> Philippe Waroquiers <philippe.waroquiers@skynet.be> changed:
>
>            What    |Removed                     |Added
> ------------------------------------------------------------
> ----------------
>                  CC|
> |philippe.waroquiers@skynet.
>                    |                            |be
>
> --- Comment #1 from Philippe Waroquiers <philippe.waroquiers@skynet.be>
> ---
> Equivalent request have already been done see e.g. bug 74899.
>
> There was even at a moment an experimental tool called omega doing this.
> The tool was however never considered working reasonably well, as it is
> difficult to detect exactly when the last pointer disappears (IIRC e.g.
> because
> copies of 'dead pointers' can be kept in registers or similar).
>
> We will keep 74899 as the place holder for this enhancement request (in
> case
> someone one day works again on the omega tool or equivalent).
>
> In the meantime, the alternative is to search the most probable last
> pointer
> or last scope having a pointer by doing leak search at regular intervals
> e.g.
> using a client request or by using gdb+vgdb and breakpoints.
>
> --
> You are receiving this mail because:
> You reported the bug.

-- 
You are receiving this mail because:
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]