Bug 1032225

Created attachment 826227 [details]
File: backtrace

Created attachment 826228 [details]
File: cgroup

Created attachment 826229 [details]
File: core_backtrace

Created attachment 826230 [details]
File: dso_list

Created attachment 826231 [details]
File: environ

Created attachment 826232 [details]
File: exploitable

Created attachment 826233 [details]
File: limits

Created attachment 826234 [details]
File: maps

Created attachment 826235 [details]
File: open_fds

Created attachment 826236 [details]
File: proc_pid_status

Created attachment 826237 [details]
File: var_log_messages

Hi.

Would it be possible to provide me a coredump?

Created attachment 826517 [details]
Full abrt dump

Are you able to reproduce this issue? Unfortunately I'm not and looking
into the coredump and backtraces it really doesn't make any sense.

> Description of problem:
> Truncated backtrace:
> Thread no. 1 (1 frames)
>  #1 getaddresses at dighost.c:3685

point to a completely different part of the source compared to what I
get from the coredump...

(gdb) bt
#0  0x0000000000000000 in ?? ()
#1  0x000000000040fd98 in send_udp (query=0x7f50d3e5b018) at dighost.c:2694
#2  0x00000000004118a3 in start_lookup () at dighost.c:1727
#3  0x0000000000413216 in onrun_callback (task=<optimized out>, event=0x0) at dighost.c:3751
#4  0x0000003325231826 in dispatch (manager=0x7f50d3e4b010) at task.c:1105
#5  run (uap=0x7f50d3e4b010) at task.c:1286
#6  0x0000003325e07f33 in start_thread (arg=0x7f50d3e45700) at pthread_create.c:309
#7  0x00000033256f4ead in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111


If you're able to reproduce it I would like to prepare a debug package for you
so I can get more information.(In reply to Juan Orti Alcaine from comment #0)

This problem is very weird, it's 100% reproducible in my main desktop PC, but I have other five F20 VMs where dig is working fine.
This computer was upgraded with fedup a month ago, and I have not got any problems with dig before.

I have reinstalled it with:
# yum remove bind-utils
# yum clean all
# yum install bind-utils

But the problem persists.

I can do all the testing you want, so if you build that debug version I'll try it.

(In reply to Juan Orti Alcaine from comment #15)
> I can do all the testing you want, so if you build that debug version I'll
> try it.

Great.

For the start, could you please:
1. attach output of 'rpm -qa'
2. run dig with option '-d' and also '-q -m' and attach both outputs

Thanks in advance.

Created attachment 830550 [details]
rpm -qa

rpm -qa

Created attachment 830551 [details]
dig -d -q -m MX gmail.com

Created attachment 830552 [details]
dig -d MX gmail.com

I think I have fixed it. Some package I had installed must be broken. I did:
yum clean all
yum distro-sync
yum reinstall bind-libs bind-utils openssl openssl-libs krb5-libs libcap libxml2 glibc

These are the versions I have got now:
bind-libs-lite-9.9.4-8.fc20.x86_64
glibc-headers-2.18-11.fc20.x86_64
libxml2-2.9.1-2.fc20.x86_64
openssl-libs-1.0.1e-30.fc20.x86_64
openssl-libs-1.0.1e-30.fc20.i686
libcap-2.22-7.fc20.i686
glibc-2.18-11.fc20.i686
bind-libs-9.9.4-8.fc20.x86_64
glibc-debuginfo-common-2.18-11.fc20.x86_64
krb5-libs-1.11.3-33.fc20.i686
libcap-2.22-7.fc20.x86_64
glibc-common-2.18-11.fc20.x86_64
libcap-ng-0.7.3-6.fc20.x86_64
krb5-libs-1.11.3-33.fc20.x86_64
glibc-devel-2.18-11.fc20.x86_64
bind-utils-9.9.4-8.fc20.x86_64
openssl-1.0.1e-30.fc20.x86_64
libxml2-python-2.9.1-2.fc20.x86_64
glibc-debuginfo-2.18-11.fc20.x86_64
glibc-2.18-11.fc20.x86_64
libxml2-devel-2.9.1-2.fc20.x86_64

(In reply to Juan Orti Alcaine from comment #20)
> I think I have fixed it. Some package I had installed must be broken. I did:
> yum clean all
> yum distro-sync
> yum reinstall bind-libs bind-utils openssl openssl-libs krb5-libs libcap
> libxml2 glibc
> 
> These are the versions I have got now:
> bind-libs-lite-9.9.4-8.fc20.x86_64
> glibc-headers-2.18-11.fc20.x86_64
> libxml2-2.9.1-2.fc20.x86_64
> openssl-libs-1.0.1e-30.fc20.x86_64
> openssl-libs-1.0.1e-30.fc20.i686
> libcap-2.22-7.fc20.i686
> glibc-2.18-11.fc20.i686
> bind-libs-9.9.4-8.fc20.x86_64
> glibc-debuginfo-common-2.18-11.fc20.x86_64
> krb5-libs-1.11.3-33.fc20.i686
> libcap-2.22-7.fc20.x86_64
> glibc-common-2.18-11.fc20.x86_64
> libcap-ng-0.7.3-6.fc20.x86_64
> krb5-libs-1.11.3-33.fc20.x86_64
> glibc-devel-2.18-11.fc20.x86_64
> bind-utils-9.9.4-8.fc20.x86_64
> openssl-1.0.1e-30.fc20.x86_64
> libxml2-python-2.9.1-2.fc20.x86_64
> glibc-debuginfo-2.18-11.fc20.x86_64
> glibc-2.18-11.fc20.x86_64
> libxml2-devel-2.9.1-2.fc20.x86_64

Great news. Strange thing is that version of your installed packages didn't
change.

Since you are not experiencing this issue any more, I'm closing this BZ as
NOTABUG. If you run into the same problem in the future and reinstalling
packages doesn't work for you, feel free to reopen this Bug.