|Message: Re: Geant4.10.02 successful compile, immediate seg-fault||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
Vaclav Stepan kindly suggested using gdb to find the stack trace. I did this and got:
(gdb) file exampleB1 Reading symbols from exampleB1...(no debugging symbols found)...done. (gdb) run Starting program: /home/phys/villaa/geant4_test/B1-build/exampleB1 exampleB1 Missing separate debuginfos, use: debuginfo-install glibc-2.12-1.166.el6_7.3.x86_64
Program received signal SIGSEGV, Segmentation fault. 0x0000003c26c0fcfd in _dl_check_map_versions () from /lib64/ld-linux-x86-64.so.2 (gdb) bt
#0 0x0000003c26c0fcfd in _dl_check_map_versions () from /lib64/ld-linux-x86-64.so.2 #1 0x0000003c26c10126 in _dl_check_all_versions () from /lib64/ld-linux-x86-64.so.2 #2 0x0000003c26c025e8 in version_check_doit () from /lib64/ld-linux-x86-64.so.2 #3 0x0000003c26c0e1f1 in _dl_receive_error () from /lib64/ld-linux-x86-64.so.2 #4 0x0000003c26c03588 in dl_main () from /lib64/ld-linux-x86-64.so.2 #5 0x0000003c26c160ae in _dl_sysdep_start () from /lib64/ld-linux-x86-64.so.2 #6 0x0000003c26c014a4 in _dl_start () from /lib64/ld-linux-x86-64.so.2 #7 0x0000003c26c00b08 in _start () from /lib64/ld-linux-x86-64.so.2 #8 0x0000000000000002 in ?? () #9 0x00007fffffffce6c in ?? () #10 0x00007fffffffce9d in ?? () #11 0x0000000000000000 in ?? ()
Yikes, looks like the linker might be at fault here. For more info I tried to see what the linker thinks of my executable:
/usr/bin/ldd: line 118: 166464 Segmentation fault (core dumped) LD_TRACE_LOADED_OBJECTS=1 LD_WARN= LD_BIND_NOW= LD_LIBRARY_VERSION=$verify_out LD_VERBOSE= "$@"
Ok, not sure what this is telling me but I think it must be a problem that the linker doesn't report to me the (shared) libraries it thinks are linked. Does ld need to be compiled with C++11 support as well? Maybe I'm not using the one from the same gcc suite, since it was loaded via a module (perhaps error there).
|Inline Depth:||Outline Depth:||Add message:|