From: Greg Kurz <groug@kaod.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
cota@braap.org, qemu-devel@nongnu.org, ehabkost@redhat.com
Subject: Re: [Qemu-devel] [RFC PATCH] tests: replace rem = sleep(time) with g_timer
Date: Fri, 11 Jan 2019 19:32:54 +0100 [thread overview]
Message-ID: <20190111193254.15849683@bahia.lan> (raw)
In-Reply-To: <3b4aa1f9-c18a-e2d7-abdd-f688bed9f4a1@redhat.com>
On Fri, 11 Jan 2019 16:41:41 +0100
Paolo Bonzini <pbonzini@redhat.com> wrote:
> On 11/01/19 16:28, Alex Bennée wrote:
> >> Why not g_usleep? It already does a while loop around nanosleep (which
> >> returns the remaining time in the wait, like select but unlike sleep and
> >> poll).
> > Yeah I'm testing that now. However I have managed to trigger:
> >
> > ERROR:tests/test-qht-par.c:20:test_qht: assertion failed (rc == 0): (35584 == 0)
>
> I think that's a good old SIGSEGV (0x8B00).
>
Hmmm... system() returns a "wait status" that can be examined using the
macros described in waitpid(2), and we have:
/* If WIFEXITED(STATUS), the low-order 8 bits of the status. */
#define __WEXITSTATUS(status) (((status) & 0xff00) >> 8)
So this rather looks like a 139 exit status to me... Not sure how
this can happen though.
> Paolo
>
next prev parent reply other threads:[~2019-01-11 18:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 14:38 [Qemu-devel] [RFC PATCH] tests: replace rem = sleep(time) with g_timer Alex Bennée
2019-01-11 14:43 ` Paolo Bonzini
2019-01-11 15:28 ` Alex Bennée
2019-01-11 15:41 ` Paolo Bonzini
2019-01-11 16:05 ` Alex Bennée
2019-01-11 16:06 ` Alex Bennée
2019-01-11 19:05 ` Eduardo Habkost
2019-01-11 18:32 ` Greg Kurz [this message]
2019-01-11 19:25 ` Alex Bennée
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190111193254.15849683@bahia.lan \
--to=groug@kaod.org \
--cc=alex.bennee@linaro.org \
--cc=cota@braap.org \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.