https://bugs.kde.org/show_bug.cgi?id=493418
Bug ID: 493418
Summary: Add bad fd usage errors for --track-fds in
ML_(fd_allowed)
Classification: Developer tools
Product: valgrind
Version: 3.22 GIT
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: ahajk...@redhat.com
Reporter: m...@klomp.org
Target Milestone: ---
In coregrind/m_syswrap/syswrap-generic.c ML_(fd_allowed) we currently have a
comment /* croak? */ after which in some situations we generate warning
messages. These should be turned into real errors like those we generate in
ML_(record_fd_close).
There are three kinds of errors to report when !isNewFd:
1. When !allowed it is an bad file descriptor (either negative or a private one
valgrind might be using)
2. When not found in allocated_fds it was an fd number never opened by the
program.
3. When found in allocated_fds, but the closed flag is set, the fd was earlier
closed.
In the last case we should have an where (opened) and a where_closed that we
can attach to the error message.
--
You are receiving this mail because:
You are watching all bug changes.
