Version-Release number of selected component: p11-kit-trust-0.20.1-1.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/bin/trust extract --format=openssl-bundle --filter=certificates --overwrite /etc/pki/ca-trust/extracted/openssl/ca-bundle.trust.crt crash_function: dlmmap_locked executable: /usr/bin/trust kernel: 3.12.5-302.fc20.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 dlmmap_locked at ../src/closures.c:460 #1 dlmmap at ../src/closures.c:506 #2 sys_alloc at ../src/dlmalloc.c:3515 #3 dlmalloc at ../src/dlmalloc.c:4245 #4 ffi_closure_alloc at ../src/closures.c:572 #5 bind_ffi_closure at virtual.c:2653 #6 init_wrapper_funcs at virtual.c:2694 #7 p11_virtual_wrap at virtual.c:2746 #8 prepare_module_inlock_reentrant at modules.c:1778 #9 p11_modules_load_inlock_reentrant at modules.c:1836
Created attachment 840965 [details] File: backtrace
Created attachment 840966 [details] File: cgroup
Created attachment 840967 [details] File: core_backtrace
Created attachment 840968 [details] File: dso_list
Created attachment 840969 [details] File: environ
Created attachment 840970 [details] File: exploitable
Created attachment 840971 [details] File: limits
Created attachment 840972 [details] File: maps
Created attachment 840973 [details] File: open_fds
Created attachment 840974 [details] File: proc_pid_status
Created attachment 840975 [details] File: var_log_messages
Thanks for reporting this bug. The trace points toward memory problems. If you are able, and on the off chance that this bug is reproducable, Could you run the command line under valgrind, and post the output? /usr/bin/trust extract --format=openssl-bundle --filter=certificates --overwrite /etc/pki/ca-trust/extracted/openssl/ca-bundle.trust.crt
It's very likely that the info request above won't be filled by the original reporter, since this came in via abrt. We'll probably need to wait for further info and/or bug reports that we can correlate this with in order to fix the issue.
For what it's worth, I believe this was a bug in libffi that was just fixed upstream with this: https://github.com/libffi/libffi/commit/d46406088d28b038a0a0f7396d9621f431482f6a