From: "Alex Bennée" <alex.bennee@linaro.org>
To: Laurent Desnogues <laurent.desnogues@gmail.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Riku Voipio <riku.voipio@iki.fi>,
Laurent Vivier <laurent@vivier.eu>
Subject: Re: [Qemu-devel] [PATCH] linux-user: fix GPROF build failure
Date: Thu, 02 May 2019 15:50:24 +0100 [thread overview]
Message-ID: <877eb86hcf.fsf@zen.linaroharston> (raw)
In-Reply-To: <CABoDooPLQAGi+gtYX+jPaZk9=OgGOLwpJdwfJML-aKMiHu3Azw@mail.gmail.com>
Laurent Desnogues <laurent.desnogues@gmail.com> writes:
> Hello,
>
> On Thu, May 2, 2019 at 11:31 AM Alex Bennée <alex.bennee@linaro.org> wrote:
>>
>> When linux-user/exit was introduced we failed to move the gprof
>> include at the same time. The CI didn't notice because it only builds
>> system emulation. Fix it for those that still find gprof useful.
>>
>> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>
> Tested-by: Laurent Desnogues <laurent.desnogues@gmail.com>
Sadly running programs then fails because of the SIG_PROF signal getting
passed to the guest. I wonder how this ever worked?
--
Alex Bennée
WARNING: multiple messages have this Message-ID (diff)
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Laurent Desnogues <laurent.desnogues@gmail.com>
Cc: Riku Voipio <riku.voipio@iki.fi>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Laurent Vivier <laurent@vivier.eu>
Subject: Re: [Qemu-devel] [PATCH] linux-user: fix GPROF build failure
Date: Thu, 02 May 2019 15:50:24 +0100 [thread overview]
Message-ID: <877eb86hcf.fsf@zen.linaroharston> (raw)
Message-ID: <20190502145024.-GIX13TlFBDnUcTwMTD61Rw7zVkrA7PttkS28TJdv2U@z> (raw)
In-Reply-To: <CABoDooPLQAGi+gtYX+jPaZk9=OgGOLwpJdwfJML-aKMiHu3Azw@mail.gmail.com>
Laurent Desnogues <laurent.desnogues@gmail.com> writes:
> Hello,
>
> On Thu, May 2, 2019 at 11:31 AM Alex Bennée <alex.bennee@linaro.org> wrote:
>>
>> When linux-user/exit was introduced we failed to move the gprof
>> include at the same time. The CI didn't notice because it only builds
>> system emulation. Fix it for those that still find gprof useful.
>>
>> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>
> Tested-by: Laurent Desnogues <laurent.desnogues@gmail.com>
Sadly running programs then fails because of the SIG_PROF signal getting
passed to the guest. I wonder how this ever worked?
--
Alex Bennée
next prev parent reply other threads:[~2019-05-02 14:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 9:27 [Qemu-devel] [PATCH] linux-user: fix GPROF build failure Alex Bennée
2019-05-02 9:27 ` Alex Bennée
2019-05-02 10:14 ` Laurent Desnogues
2019-05-02 10:14 ` Laurent Desnogues
2019-05-02 14:50 ` Alex Bennée [this message]
2019-05-02 14:50 ` Alex Bennée
2019-05-02 14:58 ` [Qemu-devel] [PATCH] linux-user: avoid treading on gprof's SIGPROF signals Alex Bennée
2019-05-02 14:58 ` Alex Bennée
2019-05-02 16:14 ` Laurent Vivier
2019-05-02 16:27 ` Laurent Desnogues
2019-05-02 16:27 ` Laurent Desnogues
2019-05-02 16:33 ` Laurent Vivier
2019-05-02 16:33 ` Laurent Vivier
2019-05-09 17:08 ` Laurent Vivier
2019-05-09 17:08 ` [Qemu-devel] [PATCH] linux-user: fix GPROF build failure Laurent Vivier
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=877eb86hcf.fsf@zen.linaroharston \
--to=alex.bennee@linaro.org \
--cc=laurent.desnogues@gmail.com \
--cc=laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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.