[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:       Philippe Waroquiers <bugzilla_noreply () kde ! org>
Date:       2018-07-31 21:21:22
Message-ID: bug-396290-17878-0YfIx9VGtY () http ! bugs ! kde ! org/
[Download RAW message or body]

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

--- Comment #11 from Philippe Waroquiers <philippe.waroquiers@skynet.be> ---
Yes, I agree that having a way to exercise the error recovery/handling
patch of an application is a very good thing to do.

IMO, it is very late now to add this, even as an exp tool.
A.o. we better discuss the desired functionality somewhat more
(e.g. to make a more general/flexible way to make various things fail
in a single 'framework/tool').

For big/huge applications, we might need a lot more control about
e.g. when to start failing (maybe something like what is available
in callgrind:   let the tool start doing something once a call to a function
has been detected, or once a certain stacktrace has been detected
etc ...

In summary: the tool as it is now is too minimal and too 'young'.

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