Thank you once again. Your reply is very very fast.
small...@aliyun.com
From: Joel Sherrill
Date: 2020-10-23 10:03
To: smallphd
CC: devel
Subject: Re: Re: rtems-5.1 source code test coverage failed
Hit send too soon
On Thu, Oct 22, 2020, 8:59 PM Joel Sherrill wrote:
On Thu, Oct 22, 2020
re qemu which should make it easier
to build.
I'd love to see this area of our tooling and ecosystem get love and grow.
:)
--joel
>
>
>> --
>> small...@aliyun.com
>>
>>
>> *From:* Joel Sherrill
>> *Date:* 2020-10-22 23:49
>> *To:* small...@a
> small...@aliyun.com
>
>
> *From:* Joel Sherrill
> *Date:* 2020-10-22 23:49
> *To:* small...@aliyun.com
> *CC:* devel
> *Subject:* Re: rtems-5.1 source code test coverage failed
>
>
> On Thu, Oct 22, 2020 at 4:02 AM small...@aliyun.com
> wrote:
&
.@aliyun.com
CC: devel
Subject: Re: rtems-5.1 source code test coverage failed
On Thu, Oct 22, 2020 at 4:02 AM small...@aliyun.com wrote:
hi, all
I want test source code coverage in qemu. There are some questions I met.
1. If compiling without -ftest-coverage, the test only produce a percent
coverage,
On Thu, Oct 22, 2020 at 4:02 AM small...@aliyun.com
wrote:
> hi, all
> I want test source code coverage in qemu. There are some questions I met.
> 1. If compiling without -ftest-coverage, the test only produce a percent
> coverage, no *.gcov file which is important to recognize which lines not
>
hi, all
I want test source code coverage in qemu. There are some questions I met.
1. If compiling without -ftest-coverage, the test only produce a percent
coverage, no *.gcov file which is important to recognize which lines not
execute.
2. If compiling with -ftest-coverage, *.gcno are created in
