5
77%
master: 77%

Ran 31 Mar 2022 01:06PM UTC

Files 58

Run time 6min

Badge

Committed 31 Mar 2022 01:01PM UTC coverage: 73.26% (-0.3%) from 73.595%

Job # CONF_OPTIONS="--enable-gcov --enable-single-obj-compilation --enable-cplusplus --disable-shared --enable-gc-assertions" CFLAGS_EXTRA="-D USE_CUSTOM_SPECIFIC" CC_FOR_CHECK=g++ MAKEFILE_TARGETS="all" MAKEFILE_TARGETS_CHECK="check" NO_CLONE_LIBATOMIC_OPS=true REPORT_COVERAGE=true TESTS_CUSTOM_RUN=true

Build Type

push

travis-ci-com

Committed by

ivmai

Commit Message

Workaround SIG_SUSPEND delivery to thread inside mutex_lock fail if TSan

Unfortunately, use of an asynchronous signal to suspend threads leads
to the situation when the signal is not delivered (is stored to
pending_signals in ThreadSanitizer runtime actually) while the target
thread is blocked in pthread_mutex_lock.  Thus, we use some synchronous
one instead (which is again unlikely to be used by clients directly).

* include/private/gc_priv.h [SIGNAL_BASED_STOP_WORLD && !SIG_SUSPEND
&& THREAD_SANITIZER] (SIG_SUSPEND): Define to SIGSYS; add comment.
* tests/disclaim.c [GC_PTHREADS] (main): Call
GC_set_thr_restart_signal(GC_get_suspend_signal()) instead of
GC_set_suspend_signal(GC_get_thr_restart_signal()) (thus, the signal
used to suspend threads is not modified in the test).

Coverage Stats

7222 of 9858 relevant lines covered (73.26%)

10267488.4 hits per line

Source Files on job 1260.5 (CONF_OPTIONS="--enable-gcov --enable-single-obj-compilation --enable-cplusplus --disable-shared --enable-gc-assertions" CFLAGS_EXTRA="-D USE_CUSTOM_SPECIFIC" CC_FOR_CHECK=g++ MAKEFILE_TARGETS="all" MAKEFILE_TARGETS_CHECK="check" NO_CLONE_LIBATOMIC_OPS=true REPORT_COVERAGE=true TESTS_CUSTOM_RUN=true)

ivmai / bdwgc / 1260 / 5
77%
master: 77%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

ivmai / bdwgc / 1260 / 5 77% master: 77%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

ivmai / bdwgc / 1260 / 5
77%
master: 77%

README BADGES
x