[PATCH] Add -e trace=memory option

[Dmitry V. Levin]

On Wed, Oct 24, 2012 at 10:01:36AM +0900, Namhyung Kim wrote:
> 2012-10-22 오전 4:25, Dmitry V. Levin 쓴 글:
> > vmsplice is not a memory mapping related.  I see it was not actually
> > changed by the patch.
> 
> But vmsplice takes memory addresses through iov->iov_base.  Isn't it memory 
> (mapping) related?

readv/writev also take struct iovec arguments, but you wouldn't add them
to the trace=memory category, would you?


-- 
ldv
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.strace.io/pipermail/strace-devel/attachments/20121024/d407d6dc/attachment.bin>