qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Pavel Dovgalyuk" <pavel.dovgaluk@gmail.com>,
	"Alex Bennée" <alex.bennee@linaro.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	"Pavel.Dovgaluk" <pavel.dovgalyuk@ispras.ru>,
	qemu-devel@nongnu.org
Subject: Re: Race with atexit functions in system emulation
Date: Thu, 2 Jul 2020 11:18:02 +0200	[thread overview]
Message-ID: <aabc2e67-944c-aa65-f6d9-24cf2df6df65@redhat.com> (raw)
In-Reply-To: <CAMgSi0G+_3ZVDMpYL5XYWvUyUUtP__zUCLPpRJ+adn3t7B8a7g@mail.gmail.com>

On 02/07/20 08:18, Pavel Dovgalyuk wrote:
> Is it true, that semihosting can be used to access (read and write) host
> files from the guest?
> In such a case it can't be used with RR for the following reasons:
> 1. We don't preserve modified files, therefore the execution result may
> change in the future runs.
> 2. Even in the case, when all the files are read only, semihosting FDs
> can't be saved, therefore it may not be used with reverse debugging.

Since there are many cases in which semihosting and RR can work together
well, I think the fix here should not be to just block semihosting.  The
replay_finish issue is just an example, there can be more atexit handlers.

Paolo



      parent reply	other threads:[~2020-07-02  9:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-01 11:05 Race with atexit functions in system emulation Alex Bennée
2020-07-01 11:14 ` Paolo Bonzini
2020-07-02  6:18 ` Pavel Dovgalyuk
2020-07-02  7:49   ` Alex Bennée
2020-07-02  7:54     ` Pavel Dovgalyuk
2020-07-02  9:18   ` Paolo Bonzini [this message]

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=aabc2e67-944c-aa65-f6d9-24cf2df6df65@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=pavel.dovgaluk@gmail.com \
    --cc=pavel.dovgalyuk@ispras.ru \
    --cc=peter.maydell@linaro.org \
    --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 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).