Version-Release number of selected component: bind-utils-9.9.2-8.P1.fc18 Additional info: backtrace_rating: 4 cmdline: dig ssl.gstatic.com @4.2.2.2 +tcp crash_function: isc_assertion_failed executable: /usr/bin/dig kernel: 3.8.3-201.fc18.x86_64 uid: 1000 var_log_messages: Mar 21 14:13:07 localhost abrt[6037]: Saved core dump of pid 6029 (/usr/bin/dig) to /var/spool/abrt/ccpp-2013-03-21-14:13:06-6029 (43139072 bytes) Truncated backtrace: Thread no. 1 (6 frames) #2 isc_assertion_failed at assertions.c:58 #3 isc__socket_recvv at socket.c:4552 #4 launch_next_query at dighost.c:2848 #5 connect_done at dighost.c:2945 #6 dispatch at task.c:1116 #7 run at task.c:1286
Created attachment 713737 [details] File: backtrace
Created attachment 713738 [details] File: cgroup
Created attachment 713739 [details] File: core_backtrace
Created attachment 713740 [details] File: dso_list
Created attachment 713741 [details] File: environ
Created attachment 713742 [details] File: limits
Created attachment 713743 [details] File: maps
Created attachment 713744 [details] File: open_fds
Created attachment 713745 [details] File: proc_pid_status
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Hi. Can you reproduce this issue? From what I inspected it looks like there was a race condition on "global_task". It has been already freed when "isc__socket_recvv()" was called. Personally without a reproducer I won't be able to hunt the cause down. From the source I don't see any way how such a situation could happen. Before "destroy_libs()", which frees the "global_task" is called, the "cancel_all()" is called, which cancels all ongoing events. Therefore when the "connect_done()" callback is called, it should return without creating any new query. connect_done() and cancel_all() are mutually exclusive and both lock the LOOKUP lock.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days