Hide Forgot
Description of problem: I was rebuilding all my ruby installs via rvm. Version-Release number of selected component: glibc-2.16-31.fc18 Additional info: reporter: libreport-2.1.4 backtrace_rating: 4 cmdline: /lib64/ld-linux-x86-64.so.2 --verify /home/jporter/.rvm/rubies/jruby-1.7.3/lib/native/x86_64-SunOS/libjffi-1.2.so crash_function: elf_get_dynamic_info dso_list: /usr/lib64/ld-2.16.so glibc-2.16-31.fc18.x86_64 (Fedora Project) 1368631644 executable: /usr/lib64/ld-2.16.so kernel: 3.9.2-200.fc18.x86_64 runlevel: N 5 uid: 1000 Truncated backtrace: Thread no. 1 (9 frames) #0 elf_get_dynamic_info at dynamic-link.h:165 #1 _dl_map_object_from_fd at dl-load.c:1428 #2 _dl_map_object at dl-load.c:2359 #3 map_doit at rtld.c:631 #4 _dl_catch_error at dl-error.c:177 #5 dl_main at rtld.c:1070 #6 _dl_sysdep_start at ../elf/dl-sysdep.c:242 #7 _dl_start_final at rtld.c:336 #8 _dl_start at rtld.c:562
Created attachment 763149 [details] File: backtrace
Created attachment 763150 [details] File: cgroup
Created attachment 763151 [details] File: core_backtrace
Created attachment 763152 [details] File: environ
Created attachment 763153 [details] File: limits
Created attachment 763154 [details] File: maps
Created attachment 763155 [details] File: open_fds
Created attachment 763156 [details] File: proc_pid_status
Created attachment 763157 [details] File: var_log_messages
What provides libjffi-1.2.so? Could you attach it to the issue please?
I can tell you right now a gem depends on it: ffi, which is used by listen I believe. As to what's providing it, I'm not sure right now.
I don't see anything in yum that supplies it, my guess is it's something from jRuby.
Please provide a copy of the DSO for analysis then.
Sorry, I'm completely new to submitting fedora tickets. What is a DSO and where can I find it or generate one?
Created attachment 763173 [details] libjffi-1.2.so libjffi from jRuby.
(In reply to Jason Porter from comment #14) > Sorry, I'm completely new to submitting fedora tickets. What is a DSO and > where can I find it or generate one? Thanks, you're doing a great job! Please note that the DSO you attached has incomplete dependencies. It has 4 relocations against symbols from libpthread: 0000000000211310 0000000a00000007 R_X86_64_JUMP_SLOT 0000000000000000 pthread_key_create + 0 0000000000211360 0000001100000007 R_X86_64_JUMP_SLOT 0000000000000000 pthread_getspecific + 0 0000000000211418 0000001c00000007 R_X86_64_JUMP_SLOT 0000000000000000 pthread_key_delete + 0 0000000000211438 0000001e00000007 R_X86_64_JUMP_SLOT 0000000000000000 pthread_setspecific + 0 However, it doesn't depend on libpthread, it only depends on libc: 0x0000000000000001 (NEEDED) Shared library: [libc.so.6] This is a common problem and shouldn't lead to a crash in the dynamic linker, but does mean the DSO is incomplete and could fail to load. I am unable to reproduce the crash with `/lib64/ld-linux-x86-64.so.2 --verify libjffi-1.2.so" on F18 with glibc-2.16-31.fc18.x86_64. I manually inspected the DSO and find nothing wrong with it. There is no indication of the cause of the failure. I'm going to mark this as CLOSED/WORKSFORME, but I'll keep an eye out for other reports.