Red Hat Bugzilla – Bug 1017487
[abrt] evolution-data-server-3.10.0-1.fc20: __libc_res_nsearch: Process /usr/libexec/evolution-source-registry was killed by signal 6 (SIGABRT)
Last modified: 2015-06-29 08:36:16 EDT
Description of problem:
Opened Evolution, received abrt.
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (8 frames)
#5 __libc_res_nsearch at res_query.c:392
#6 _nss_dns_gethostbyname4_r at nss_dns/dns-host.c:314
#7 gaih_inet at ../sysdeps/posix/getaddrinfo.c:850
#8 getaddrinfo at ../sysdeps/posix/getaddrinfo.c:2405
#9 do_lookup_by_name at gthreadedresolver.c:81
#10 g_task_thread_pool_thread at gtask.c:1245
#12 g_thread_proxy at gthread.c:798
#14 clone at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
Created attachment 810242 [details]
Created attachment 810243 [details]
Created attachment 810244 [details]
Created attachment 810245 [details]
Created attachment 810246 [details]
Created attachment 810247 [details]
Created attachment 810248 [details]
Created attachment 810249 [details]
Created attachment 810250 [details]
Thanks for a bug report. I see many threads trying to resolve various addresses, when one of the threads crashed on a (software) memory corruption. It's hard to tell why it happened, the actual corruption could happen anytime before it was recognized by libc, same as the same memory corruption reason can reveal itself on different places.
Due to it, could you try to run evolution under valgrind, it'll be awfully slow due to all memory checking, though the more you let it run the better, and upload the log here, please? The valgrind command looks like this:
$ G_SLICE=always-malloc valgrind --num-callers=50 evolution &>log.txt
Even valgrind doesn't catch every memory issue, it is good in catching many types of memory corruption.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.