Implemented -e trace=%clock option

[Dmitry V. Levin]

On Mon, Mar 13, 2017 at 11:20:30PM +0530, Rishi Bhatt wrote:
> Hey does $STRACE in init.sh is doing this:strace -e trace=%clock
> ./clock_nanosleep > /dev/null
> 
> So  my problem here is the output in .tmp file is correct but the .exp has
> the print statements from ./clock_nanosleep so for matching .exp and .tmp
> files i have to filter setitimer string from .exp file?
> 
> (< setitimer(ITIMER_REAL, {it_interval={tv_sec=0, tv_usec=222222},
> it_value={tv_sec=0, tv_usec=111111}}, NULL) = 0)
> 
> Also please give me some idea about if i want to implement a test case, i
> am confuse in ,what should be the output and from whom i have to compare
> it?  Or what should be my basic approach to implement test cases.
> 
> Sorry if this thing is too easy but well i am not just getting the crux of
> it.

Looks like you don't understand the fact that you are trying to reuse a
part of clock_nanosleep.test for your new test, and you don't understand
that it doesn't work as easily as with other clock_* tests you are trying
to reuse because for some obscure reason clock_nanosleep.test doesn't
limit itself with testing of clock_nanosleep decoder.


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