On Wed 02 May 2012 23:15, l...@gnu.org (Ludovic Courtès) writes: > Andy Wingo <wi...@pobox.com> skribis: > >> Some versions of libgc do produce one SIGSEGV at startup, when >> determining certain aspects of the process's memory layout. Just FYI :) > > Woow. :-) Do you know which versions/arches are affected?
I don't recall. It's an expected SIGSEGV, not an erroneous one. I get it: Program received signal SIGSEGV, Segmentation fault. 0x00007ffff732f4f6 in GC_find_limit_with_bound (p=0x401f4c "", up=0, bound=0x0) at os_dep.c:957 warning: Source file is more recent than executable. 957 GC_noop1((word)(*result)); (gdb) bt #0 0x00007ffff732f4f6 in GC_find_limit_with_bound (p=0x401f4c "", up=0, bound=0x0) at os_dep.c:957 #1 0x00007ffff732f5f9 in GC_init_linux_data_start () at os_dep.c:472 #2 0x00007ffff732df53 in GC_init () at misc.c:899 #3 GC_init () at misc.c:643 #4 0x00007ffff7ee59ed in scm_storage_prehistory () at gc.c:639 Regards, Andy -- http://wingolog.org/
