From: "Alex Bennée" <alex.bennee@linaro.org>
To: Pavel Dovgalyuk <pavel.dovgalyuk@ispras.ru>
Cc: NDNF <arkaisp2021@gmail.com>,
arkadiy.ivanov@ispras.ru, qemu-devel@nongnu.org,
pavel.dovgaluk@ispras.ru
Subject: Re: [PATCH v3 0/3] plugins: add a drcov plugin
Date: Wed, 19 Jan 2022 10:17:57 +0000 [thread overview]
Message-ID: <87lezc81tv.fsf@linaro.org> (raw)
In-Reply-To: <155b5061-bc5b-6a23-ea5a-1d0fd367dc16@ispras.ru>
Pavel Dovgalyuk <pavel.dovgalyuk@ispras.ru> writes:
> On 25.10.2021 22:03, Alex Bennée wrote:
>> NDNF <arkaisp2021@gmail.com> writes:
>>
>>> These patches adds the ability to generate files in drcov format.
>>> Primary goal this scripts is to have coverage
>>> logfiles thatwork in Lighthouse.
>> Queued with some fixes to plugins/next, thanks.
>>
>
> ping
I would still like to find a decent way of testing these coverage files.
I looked at a number of FLOSS tools and I think radare2 can handle the
drcov format but I couldn't get anything out of it.
I'll be posting the state of my plugins/next tree soon and we can get
some final reviews before submitting the PR.
--
Alex Bennée
prev parent reply other threads:[~2022-01-19 10:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 16:06 [PATCH v3 0/3] plugins: add a drcov plugin NDNF
2021-10-22 16:07 ` [PATCH v3 1/3] src/plugins: sorted list NDNF
2021-10-25 15:48 ` Alex Bennée
2021-10-22 16:07 ` [PATCH v3 2/3] This patch adds helper functions to the drcov plugin NDNF
2021-10-22 16:07 ` [PATCH v3 3/3] contrib/plugins: add a " NDNF
2021-10-25 19:03 ` [PATCH v3 0/3] plugins: " Alex Bennée
2022-01-19 9:35 ` Pavel Dovgalyuk
2022-01-19 10:17 ` Alex Bennée [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=87lezc81tv.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=arkadiy.ivanov@ispras.ru \
--cc=arkaisp2021@gmail.com \
--cc=pavel.dovgaluk@ispras.ru \
--cc=pavel.dovgalyuk@ispras.ru \
--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.