On 04/03/14 17:41, William Manley wrote:
> + case VIDIOC_TRY_FMT:
> + case VIDIOC_S_FMT:
> + {
> + /* TODO: work out how strace deals with inout arguments
> and
> + implement */
> + return 0;
> + }
I'd quite like to implement this. How should I go about displaying this
given that it uses inout arguments? e.g. printing the contents of the
struct passed as an argument on both entering(tcp) and exiting(tcp)
seems like a good idea but I'm worried that it will look confusing to
the user.
Thanks
Will
------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries. Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
Strace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/strace-devel
