Re: gcov coverage data not full with immediate stop

Поиск
Список
Период
Сортировка
От Ashutosh Bapat
Тема Re: gcov coverage data not full with immediate stop
Дата
Msg-id CAExHW5u_0u=YdnvaRYNrYBFxJowZai7L4u5LiYUJY8=swS1i6w@mail.gmail.com
обсуждение исходный текст
Ответ на Re: gcov coverage data not full with immediate stop  (Alexander Lakhin <exclusion@gmail.com>)
Ответы Re: gcov coverage data not full with immediate stop  (Michael Paquier <michael@paquier.xyz>)
Список pgsql-hackers
Дерево обсуждения 
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 по дате отправления:

Предыдущее
От: Amit Kapila
Дата:
Сообщение: Re: Parallel copy
Следующее
От: Julien Rouhaud
Дата:
Сообщение: Re: Add "-Wimplicit-fallthrough" to default flags (was Re: pgsql:Support FETCH FIRST WITH TIES)