[Gc] Re: [PATCH] Dealing with `.data.rel.ro'

Petter Urkedal urkedal at nbi.dk
Sat May 23 05:12:19 PDT 2009


On 2009-05-23, Petter Urkedal wrote:
> This revision causes segfault for hugetest and threadleaktest test on
> Linux x86_64:

After I --enable-gc-assertions I get:

Assertion failure: /home/urkedal/proj/bdwgc-pu/mark.c:905
Assertion failure: /home/urkedal/proj/bdwgc-pu/mark.c:905
assertion failure
/bin/sh: line 4:  9102 Aborted                 (core dumped) ${dir}$tst
FAIL: hugetest
Assertion failure: /home/urkedal/proj/bdwgc-pu/mark.c:905
assertion failure
Assertion failure: /home/urkedal/proj/bdwgc-pu/mark.c:905
assertion failure
/bin/sh: line 4:  9130 Aborted                 (core dumped) ${dir}$tst
FAIL: threadleaktest

Some info from the debugger (ask if you need more):

(gdb) p/x *top
$2 = {mse_start = 0x7f9ba26eb9b8, mse_descr = 0x1c57f24969288058}
(gdb) p/x GC_greatest_plausible_heap_addr
$3 = 0x2643a0a
(gdb) p/x GC_least_plausible_heap_addr
$4 = 0x631ff8

I also noted that smashtest complains about smashed heap objects:

GC_check_heap_block: found smashed heap objects:
0x63ffe8 in or near object at 0x63ffc0(/home/urkedal/proj/bdwgc-pu/tests/smash_test.c:21, sz=40)
GC_check_heap_block: found smashed heap objects:
0x63ffe8 in or near object at 0x63ffc0(/home/urkedal/proj/bdwgc-pu/tests/smash_test.c:21, sz=40)
GC_check_heap_block: found smashed heap objects:
0x6e3f98 in or near object at 0x6e3f70(/home/urkedal/proj/bdwgc-pu/tests/smash_test.c:21, sz=40)
0x63ffe8 in or near object at 0x63ffc0(/home/urkedal/proj/bdwgc-pu/tests/smash_test.c:21, sz=40)
PASS: smashtest

Shouldn't smashtest return a non-zero exit status in this case?

Petter


More information about the Gc mailing list