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

List:       kde-bugs-dist
Subject:    [valgrind] [Bug 396290] [PATCH] Possible tool - allocfail
From:       <bugzilla_noreply () kde ! org>
Date:       2018-08-23 9:09:42
Message-ID: bug-396290-17878-gi3PouCCu5 () http ! bugs ! kde ! org/
[Download RAW message or body]

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

--- Comment #21 from roger.light@cedalo.com ---
I'll make the if explicit changes.

I still need to have a proper go over the documentation to tie it together as a
whole and give more examples of all the options and how they interact - I'll
cover the point you mention then. I haven't changed the bulk of what is written
there since adding these new controls.

Instrumentation certainly takes a bit to get your head around, I don't think
I've done that quite yet. I tested the entry/return on a simple example and it
worked, but I've just tried something more realistic and you are correct that
it fails - it does not detect the return point. I have spent time looking at
the callgrind code, but it is involved to say the least. I'll dig into it some
more.

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