• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

ivmai / bdwgc / 1249 / 4
73%
master: 77%

Build:
Build:
LAST BUILD BRANCH: draft-travis
DEFAULT BRANCH: master
Ran 16 Mar 2022 09:36AM UTC
Files 58
Run time 19s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

16 Mar 2022 08:44AM UTC coverage: 73.103% (+0.3%) from 72.829%
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

push

travis-ci-com

ivmai
Fix SIGSEGV caused by dropped stack access from child process in gctest
(a cherry-pick of commit 673f0cf3f from 'master')

Issue #256 (bdwgc).

Previously, a local variable was passed in gctest to
GC_move_disappearing_link as a link to clear, this led to a memory
access violation during garbage collection in the child process
if the fork occurred between  GC_move_disappearing_link(..., &new_link)
and GC_unregister_disappearing_link(&new_link).

This commit changes the mentioned local variable (new_link) use - now
it contains a pointer to a heap-allocated link rather then containing
just a link.

* tests/test.c (mktree): Change type of new_link from void* to
void**; initialize it to GC_NEW(void*) and ensure it is non-null;
replace new_link with *new_link; add comment new_link object is
reclaimed correctly even if the thread is dropped in the child
process between GC_move_disappearing_link(new_link) and
GC_unregister_disappearing_link.

7159 of 9793 relevant lines covered (73.1%)

11219237.21 hits per line

Source Files on job 1249.4 (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)
  • Tree
  • List 0
  • Changed 35
  • Source Changed 2
  • Coverage Changed 35
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 816
  • Travis Job 1249.4
  • 2d93163e on github
  • Prev Job for 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 on release-8_2 (#1247.4)
  • Next Job for 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 on release-8_2 (#1259.4)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc