Postgres Pro
Downloads
Home   >   mailing lists

Re: gcov coverage data not full with immediate stop - Mailing list pgsql-hackers

From Ashutosh Bapat
Subject Re: gcov coverage data not full with immediate stop
Date
Msg-id CAExHW5u_0u=YdnvaRYNrYBFxJowZai7L4u5LiYUJY8=swS1i6w@mail.gmail.com
Whole thread Raw
In response to Re: gcov coverage data not full with immediate stop  (Alexander Lakhin <exclusion@gmail.com>)
Responses Re: gcov coverage data not full with immediate stop  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
Tree view 
On Mon, May 11, 2020 at 2:30 PM Alexander Lakhin <exclusion@gmail.com> wrote:

>
> But I can confirm that calling __gcov_flush() in SignalHandlerForCrashExit() really improves a code coverage report.
>
> Finally I've managed to get an expected coverage when I performed $node_standby->stop() (but __gcov_flush() in
SignalHandlerForCrashExit()helps too).
 

What happens if a coverage tool other than gcov is used? From that
perspective, it's better to perform a clean shutdown in the TAP tests
instead of immediate if that's possible.

-- 
Best Wishes,
Ashutosh Bapat

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Parallel copy
Next
From: Julien Rouhaud
Date:
Subject: Re: Add "-Wimplicit-fallthrough" to default flags (was Re: pgsql:Support FETCH FIRST WITH TIES)