Close #3437.
---
c-user/fatal_error.rst | 4
1 file changed, 4 insertions(+)
diff --git a/c-user/fatal_error.rst b/c-user/fatal_error.rst
index 7945030..305de23 100644
--- a/c-user/fatal_error.rst
+++ b/c-user/fatal_error.rst
@@ -127,6 +127,10 @@ RTEMS_FATAL_SOURCE_SMP (10)
RTEMS_FATAL_SOUR
An invalid heap usage such as a double free is usually a fatal error
since this indicates a use after free. Replace the use of printk() in
free() with a fatal error.
Update #3437.
---
cpukit/include/rtems/score/interr.h | 7 +++
cpukit/libcsupport/src/free.c | 7 +--
2 files change
---
c-user/region_manager.rst | 19 ++-
1 file changed, 10 insertions(+), 9 deletions(-)
diff --git a/c-user/region_manager.rst b/c-user/region_manager.rst
index 1bebd8a..6a894d7 100644
--- a/c-user/region_manager.rst
+++ b/c-user/region_manager.rst
@@ -255,17 +255,22 @@ DIRECTIVE
Just chatted with Chris. The coverage BSP ini file was a temporary
measure as I thought.
Make a list of all the ideas we have had for improvements. We want
the code to get onto master.
The list should be converted to Trac tickets very soon. Then we can
decide which are critical for GSoC, which Ch
On Fri, 1 Jun 2018, 03:40 Joel Sherrill, wrote:
>
>
> On Thu, May 31, 2018 at 4:57 PM, Vijay Kumar Banerjee <
> vijaykumar9...@gmail.com> wrote:
>
>> On 1 June 2018 at 02:50, Joel Sherrill wrote:
>>
>>>
>>>
>>> On Thu, May 31, 2018 at 4:15 PM, Cillian O'Donnell <
>>> cpodonne...@gmail.com> wrote
On Thu, May 31, 2018 at 4:57 PM, Vijay Kumar Banerjee <
vijaykumar9...@gmail.com> wrote:
> On 1 June 2018 at 02:50, Joel Sherrill wrote:
>
>>
>>
>> On Thu, May 31, 2018 at 4:15 PM, Cillian O'Donnell > > wrote:
>>
>>>
>>>
>>> On Thu, 31 May 2018, 22:03 Vijay Kumar Banerjee, <
>>> vijaykumar9...@gm
On 1 June 2018 at 02:50, Joel Sherrill wrote:
>
>
> On Thu, May 31, 2018 at 4:15 PM, Cillian O'Donnell
> wrote:
>
>>
>>
>> On Thu, 31 May 2018, 22:03 Vijay Kumar Banerjee, <
>> vijaykumar9...@gmail.com> wrote:
>>
>>> On 1 June 2018 at 02:14, Cillian O'Donnell
>>> wrote:
>>>
There is now a
On Thu, May 31, 2018 at 4:15 PM, Cillian O'Donnell
wrote:
>
>
> On Thu, 31 May 2018, 22:03 Vijay Kumar Banerjee,
> wrote:
>
>> On 1 June 2018 at 02:14, Cillian O'Donnell wrote:
>>
>>> There is now a seperate bsp config for coverage, leon3-qemu-cov. That is
>>> enough to trigger coverage now and
On Thu, 31 May 2018, 22:03 Vijay Kumar Banerjee,
wrote:
> On 1 June 2018 at 02:14, Cillian O'Donnell wrote:
>
>> There is now a seperate bsp config for coverage, leon3-qemu-cov. That is
>> enough to trigger coverage now and --coverage could be reserved for picking
>> sets, probably renamed to --
On 1 June 2018 at 02:15, Gedare Bloom wrote:
> On Thu, May 31, 2018 at 4:44 PM, Cillian O'Donnell
> wrote:
> > There is now a seperate bsp config for coverage, leon3-qemu-cov. That is
> > enough to trigger coverage now and --coverage could be reserved for
> picking
> > sets, probably renamed to
On 1 June 2018 at 02:14, Cillian O'Donnell wrote:
> There is now a seperate bsp config for coverage, leon3-qemu-cov. That is
> enough to trigger coverage now and --coverage could be reserved for picking
> sets, probably renamed to --coverage-sets=... Or require sets to be chosen
> --coverage-sets
On Thu, May 31, 2018 at 4:44 PM, Cillian O'Donnell
wrote:
> There is now a seperate bsp config for coverage, leon3-qemu-cov. That is
> enough to trigger coverage now and --coverage could be reserved for picking
> sets, probably renamed to --coverage-sets=... Or require sets to be chosen
> --covera
There is now a seperate bsp config for coverage, leon3-qemu-cov. That is
enough to trigger coverage now and --coverage could be reserved for picking
sets, probably renamed to --coverage-sets=... Or require sets to be chosen
--coverage-sets=all or specific sets --coverage-sets=score,sapi,core
On Th
On 1 June 2018 at 01:57, Cillian O'Donnell wrote:
> So is it checking whether it's --coverage or --coverage=set1,set2? Are
> those the 2 possibilities your checking?
>
> Yes, right. :)
> On Thu, 31 May 2018, 20:52 Vijay Kumar Banerjee,
> wrote:
>
>> On 1 June 2018 at 01:19, Gedare Bloom wrote:
So is it checking whether it's --coverage or --coverage=set1,set2? Are
those the 2 possibilities your checking?
On Thu, 31 May 2018, 20:52 Vijay Kumar Banerjee,
wrote:
> On 1 June 2018 at 01:19, Gedare Bloom wrote:
>
>> On Thu, May 31, 2018 at 3:47 PM, Vijay Kumar Banerjee
>> wrote:
>> > On 1
On 1 June 2018 at 01:19, Gedare Bloom wrote:
> On Thu, May 31, 2018 at 3:47 PM, Vijay Kumar Banerjee
> wrote:
> > On 1 June 2018 at 01:07, Cillian O'Donnell
> wrote:
> >>
> >>
> >>
> >> On 31 May 2018 at 19:07, Vijay Kumar Banerjee >
> >> wrote:
> >>>
> >>> Add support in tester to run covoar
On Thu, May 31, 2018 at 3:47 PM, Vijay Kumar Banerjee
wrote:
> On 1 June 2018 at 01:07, Cillian O'Donnell wrote:
>>
>>
>>
>> On 31 May 2018 at 19:07, Vijay Kumar Banerjee
>> wrote:
>>>
>>> Add support in tester to run covoar and generate an html report to
>>> display
>>> the summary of the cover
On 1 June 2018 at 01:07, Cillian O'Donnell wrote:
>
>
> On 31 May 2018 at 19:07, Vijay Kumar Banerjee
> wrote:
>
>> Add support in tester to run covoar and generate an html report to display
>> the summary of the coverage reports generated from covoar.
>>
>> Co-authored-by : Cillian O'Donnell
>
On 31 May 2018 at 19:07, Vijay Kumar Banerjee
wrote:
> Add support in tester to run covoar and generate an html report to display
> the summary of the coverage reports generated from covoar.
>
> Co-authored-by : Cillian O'Donnell
> ---
> tester/rt/coverage.py | 379
> +++
Add support in tester to run covoar and generate an html report to display
the summary of the coverage reports generated from covoar.
Co-authored-by : Cillian O'Donnell
---
tester/rt/coverage.py | 379 ++
tester/rt/test.py
20 matches
Mail list logo