pike.git/ src/ gc.c

2018-11-30

2018-11-30 17:45:36 by Tobias S. Josefowitz <tobij@tobij.de>

• bfbcce52b0455e163fcf5de1a7fa27c8835c4e88 (5 lines) (+5/-0) ^{[ Show | Annotate ]}
  Branch: bill/debugger-concept

GC: Avoid ordering the mc_marker queue on uninitialized fields

Both Pike.count_memory() (sometimes) and Pike.identify_cycle() (always)
ordered the mc_marker queue on uninitialized data. While apparently not
inherently problematic, initializing helps to avoid valgrind false
positives.

5224:       if (!ref_to) {    ref_to = my_make_mc_marker (thing, visit_fn, extra); +  ref_to->la_count = 0; /* initialize so the queue doesn't order on +  uninitialized memory (... valgrind) */    MC_DEBUG_MSG (ref_to, "got new thing");    }    else if (ref_to->flags & MC_FLAG_INTERNAL) {
6047:    }       ref_to = my_make_mc_marker(dst, visit_dst, extra); +  ref_to->la_count = 0; /* initialize just so the queue doesn't order on +  uninitialized memory (... valgrind) */       if (type != PIKE_T_UNKNOWN) {    /* NB: low_mapping_insert() for object indices may throw errors