Hi,
On Tue, Mar 14, 2017 at 10:18:27PM +0530, Rishi Bhatt wrote:
> Hey,
> I have implemented clock.test test case,and ya clock_nanosleep's test
> has setitimer as one of the option,so i did the same and and included
> setitimer in my test case so that $LOG and $EXP have the same out
> put. But we
On Tue, Mar 14, 2017 at 4:42 PM, Leixiang Wu wrote:
> Hi,
>
> I am using strace to capture system call traces of a program. I would like
> to capture session ID and process group ID. Is this possible in strace? I
> looked the man page. It doens't say anything about those two process state
> inform
Hi,
I am using strace to capture system call traces of a program. I would like
to capture session ID and process group ID. Is this possible in strace? I
looked the man page. It doens't say anything about those two process state
information.
Best,
Leixiang Wu
--
Hey,
I have implemented clock.test test case,and ya clock_nanosleep's test
has setitimer as one of the option,so i did the same and and included
setitimer in my test case so that $LOG and $EXP have the same out
put. But well i am still in doubt that why printing setitimer is
necessary in clock_nan
run_prog ./$i > /dev/null
run_strace -a$w -e trace=%clock,setitimer ./clock_nanosleep > "$EXP"
match_diff "$LOG" "$EXP"
On Tue, Mar 14, 2017 at 3:45 PM, Rishi Bhatt
wrote:
> Well i got it so i have done something like this:
>
> run_prog ./$i > /dev/null
> run_strace -a$w -e trace
Well i got it so i have done something like this:
run_prog ./$i > /dev/null
run_strace -a$w -e trace=%clock,setitimer ./$i > "$EXP"
match_diff "$LOG" "$EXP"
On Tue, Mar 14, 2017 at 8:04 AM, Dmitry V. Levin wrote:
> On Mon, Mar 13, 2017 at 11:20:30PM +0530, Rishi Bhatt wrote:
> > Hey doe
On Tue, Mar 14, 2017 at 01:16:23AM -0400, Mike Frysinger wrote:
> On 14 Mar 2017 00:57, Mike Frysinger wrote:
> > so there's a disagreement in the overall system somewhere.
> > i'd assume either the kernel's implementation of access_ok,
> > or gcc's handling of the inline assembly.
> >
> > once i
