[PATCH v7 4/4] tests: check status qualifier

[Dmitry V. Levin]

On Sun, Jul 07, 2019 at 05:31:26PM +0200, Paul Chaignon wrote:
> On Sun, Jul 07, 2019 at 01:25:14PM +0300, Dmitry V. Levin wrote:
> > On Sat, Jul 06, 2019 at 09:20:15AM +0200, Paul Chaignon wrote:
[...]
> You meant the status-unfinished test, not status-successful, right?

Definitely.

> > the following behaviour is very likely on that system:
> > 
> > $ ../strace -qf -enanosleep ./status-unfinished >/dev/null
> > [pid 24680] nanosleep({tv_sec=123, tv_nsec=0},  <unfinished ...>
> > [pid 24681] nanosleep({tv_sec=0, tv_nsec=12345}, NULL) = 0
> > [pid 24680] <... nanosleep resumed>NULL) = ? ERESTART_RESTARTBLOCK (Interrupted by signal)
> 
> Looking at the code of syscall_exiting_trace(), I'm not quite sure where
> this NULL is coming from...?  There shouldn't be anything printed between
> the call to print_syscall_resume() and the subsequent closing parenthesis.

It comes from nanosleep parser.  Nothing special, just looks ugly.

> As for the ERESTART_RESTARTBLOCK, should we just handle that case in the
> .c test?

It's complicated by the fact that we have no information whether that case
has happened or not.

> > ../strace: Stray PTRACE_EVENT_EXEC from pid 24680, trying to recover...
> > +++ superseded by execve in pid 24681 +++
> > +++ exited with 0 +++


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