https://bugs.kde.org/show_bug.cgi?id=362680
e...@ozhiker.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |CONFIRMED
Ever confirmed|0 |1
CC| |e...@ozhiker.com
--- Comment #1 from e...@ozhiker.com ---
Hi Valgrind architects,
I have implemented a fix for this bug / feature request - my patch generates
proper errors using VG_(unique_error).
These can then influence the error count and exit code, and can also be
suppressed.
Since "track-fds" is part of coregrind, this involves resurrecting CoreErrors
and adding functions for the error parts of the tool interface to the core.
These new functions redirect CoreErrors to the correct part of the core.
i.e. Adding to m_errormgr.c:
core_before_pp_Error()
core_get_error_name()
core_update_extra()
core_pp_Error()
core_eq_Error()
core_recognised_suppression()
core_read_extra_suppression_info()
core_get_extra_suppression_info()
These functions then redirect track-fds errors to functions in
syswrap-generic.c
Is this scheme acceptable?
I will attach a patch for this shortly.
--
You are receiving this mail because:
You are watching all bug changes.
