From: Arnaud Patard (Rtp) <arnaud.patard@rtp-net.org>
To: Ulrich Hecht <uli@suse.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] linux-user and signal handling
Date: Thu, 18 Jun 2009 17:17:39 +0200 [thread overview]
Message-ID: <87bpolsh9o.fsf@lechat.rtp-net.org> (raw)
In-Reply-To: <200906181526.04570.uli@suse.de> (Ulrich Hecht's message of "Thu\, 18 Jun 2009 15\:26\:04 +0200")
Ulrich Hecht <uli@suse.de> writes:
> On Thursday 18 June 2009, Arnaud Patard wrote:
>> When doing some ltp syscall testing with arm-linux-user, some tests
>> are failing with messages like that :
>>
>> qemu: uncaught target signal 6 (Aborted) - core dumped
>> Child did not return core bit set!
>> iteration 0, exit stat = 0x6
>> Core = 0, sig = 6, ex = 0
>> abort01 1 FAIL : Test failed
> [...]
>> Has someone an idea how to fix the problem ?
>
> Have you considered that the test might be broken? I tried it, and it
> fails in the same way on native AMD64 and i386...
well, of course. Before looking at the ltp test failures, the first
thing I'm doing is to check if the test is ok on the host without
qemu. It would be quite stupide to try to solve tests in qemu if they're
failing on the host system without qemu.
As regards the signal tests, they're ok here (it was on a x86 box) :
tag=abort01 stime=1245253207
cmdline="ulimit -c 1024;abort01"
contacts=""
analysis=exit
initiation_status="ok"
<<<test_output>>>
abort01 1 PASS : Test passed
Arnaud
next prev parent reply other threads:[~2009-06-18 15:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 11:56 [Qemu-devel] linux-user and signal handling Arnaud Patard
2009-06-18 13:26 ` Ulrich Hecht
2009-06-18 15:17 ` Arnaud Patard [this message]
2009-06-18 15:35 ` Ulrich Hecht
2009-06-18 16:08 ` Ulrich Hecht
2009-06-18 16:27 ` Arnaud Patard
2009-06-18 17:14 ` Daniel Jacobowitz
2009-06-18 18:45 ` Riku Voipio
2009-06-18 19:40 ` Arnaud Patard
2009-06-19 8:08 ` Riku Voipio
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=87bpolsh9o.fsf@lechat.rtp-net.org \
--to=arnaud.patard@rtp-net.org \
--cc=qemu-devel@nongnu.org \
--cc=uli@suse.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).