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

List:       kde-bugs-dist
Subject:    [valgrind] [Bug 320895] add fanotify support (patch included)
From:       Heinrich Schuchardt <xypron.glpk () gmx ! de>
Date:       2013-07-01 17:50:15
Message-ID: bug-320895-17878-MPnYivhb72 () http ! bugs ! kde ! org/
[Download RAW message or body]

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

--- Comment #14 from Heinrich Schuchardt <xypron.glpk@gmx.de> ---
Hello Bart,

>> It might be challenging to get this right though.
If you could upload the proposed patches to trunk this would be an incomplete
solution but at least users would be able to analyze programs containing
fanotify API calls.

>> modify the post-section of any system call that reads
There is no guarantee for the length of structure fanotify_event_metadata.
Instead fanotify_event_metadata->event_len is used to find the next entry in
the read buffer with macro FAN_EVENT_NEXT(meta, len).

The solution desired hence would require to reference <sys/fanotify.h> as 
Above you said "It is important not to use glibc headers in Valgrind source
files." What is your view on this?

Could you, please, update the status of this bug to confirmed.

Best regards

Heinrich Schuchardt

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