Red Hat Bugzilla – Bug 981143
[abrt] glibc-2.17-11.fc19: elf_get_dynamic_info: Process /usr/lib64/ld-2.17.so was killed by signal 11 (SIGSEGV)
Last modified: 2016-11-24 07:26:10 EST
Description of problem:
I'm not sure how this happened. I was running rvm to build jruby in my home directory and suddenly got this error signal.
Version-Release number of selected component:
cmdline: /lib64/ld-linux-x86-64.so.2 --verify /home/jmbrooks/.rvm/rubies/jruby-1.7.4/lib/native/x86_64-SunOS/libjffi-1.2.so
dso_list: /usr/lib64/ld-2.17.so glibc-2.17-11.fc19.x86_64 (Fedora Project) 1372882988
runlevel: N 5
Thread no. 1 (9 frames)
#0 elf_get_dynamic_info at get-dynamic-info.h:89
#1 _dl_map_object_from_fd at dl-load.c:1431
#2 _dl_map_object at dl-load.c:2378
#3 map_doit at rtld.c:624
#4 _dl_catch_error at dl-error.c:177
#5 dl_main at rtld.c:1064
#6 _dl_sysdep_start at ../elf/dl-sysdep.c:241
#7 _dl_start_final at rtld.c:329
#8 _dl_start at rtld.c:555
Potential duplicate: bug 976100
Created attachment 768596 [details]
Created attachment 768597 [details]
Created attachment 768598 [details]
Created attachment 768599 [details]
Created attachment 768600 [details]
Created attachment 768601 [details]
Created attachment 768603 [details]
Created attachment 768604 [details]
Created attachment 768605 [details]
As noted this looks exactly the same as bug 976100.
What's odd is that the crash isn't in exactly the same place but it's still the same DSO and still while running rvm.
This is starting to correlate in the direction of rvm causing memory corruption that in turn causes the loader to crash. I still can't reproduce this locally.
Can you clarify something for me?
How did you install rvm?
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.