From: Peter Maydell <peter.maydell@linaro.org>
To: Andreas Schwab <schwab@suse.de>
Cc: qemu-devel@nongnu.org
Subject: Re: linux-user crash in python test
Date: Mon, 24 Jun 2024 15:26:44 +0100 [thread overview]
Message-ID: <CAFEAcA_ntKQpvtrzYubvsWKy+e3R==ZfUB=TeqDc7rnbT7oiww@mail.gmail.com> (raw)
In-Reply-To: <mvmjziepgn8.fsf@suse.de>
On Mon, 24 Jun 2024 at 15:20, Andreas Schwab <schwab@suse.de> wrote:
>
> $ /usr/bin/python3.11 -m unittest -v test.test_signal.StressTest.test_stress_modifying_handlers
> test_stress_modifying_handlers (test.test_signal.StressTest.test_stress_modifying_handlers) ... ok
>
> ----------------------------------------------------------------------
> Ran 1 test in 0.526s
>
> OK
> $ qemu-x86_64 /usr/bin/python3.11 -m unittest -v test.test_signal.StressTest.test_stress_modifying_handlers
> test_stress_modifying_handlers (test.test_signal.StressTest.test_stress_modifying_handlers) ... qemu: uncaught target signal 11 (Segmentation fault) - core dumped
> Segmentation fault (core dumped)
Just to check, does the python you're running this on
have the change from
https://github.com/python/cpython/pull/110659
? That is a fix for a bug in this test which was found after 3.11
released but was backported to the 3.11 branch, and which
(if I'm reading the bug reports correctly) might cause either
test failures or segfaults.
Though it also wouldn't surprise me if this was a QEMU bug.
thanks
-- PMM
next prev parent reply other threads:[~2024-06-24 14:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 14:19 linux-user crash in python test Andreas Schwab
2024-06-24 14:26 ` Peter Maydell [this message]
2024-06-24 15:05 ` Andreas Schwab
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='CAFEAcA_ntKQpvtrzYubvsWKy+e3R==ZfUB=TeqDc7rnbT7oiww@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=schwab@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).