Bug 473297 - host(1) segfault
host(1) segfault
Status: CLOSED DUPLICATE of bug 452060
Product: Fedora
Classification: Fedora
Component: bind (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Adam Tkac
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-11-27 10:31 EST by Jakub Hrozek
Modified: 2013-04-30 19:42 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-12-02 03:48:49 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
b2zipped core file (149.66 KB, application/x-bzip)
2008-11-27 10:31 EST, Jakub Hrozek
no flags Details

  None (edit)
Description Jakub Hrozek 2008-11-27 10:31:31 EST
Created attachment 324893 [details]
b2zipped core file

Description of problem:
host(1) segfaults for me when asking about certain servers, right before it should output MX records:

[root@ipa-server local]# host redhat.com
redhat.com has address
Segmentation fault

This is a virtual machine, using libvirt's NAT network config. I have bind running on that machine that provides DNS for my virtual machines, unknown requests are forwarded to libvirt's default DNS:

AFAIK the segfault occurs only for requests from outside - i.e. when the local bind forwards the request.

Version-Release number of selected component (if applicable):

How reproducible:
not always, but often enough.

Steps to Reproduce:
1. host redhat.com
Actual results:

Expected results:
no segfault

Additional info:
core file attached. gdb session:

(gdb) r redhat.com
Starting program: /usr/bin/host redhat.com
[Thread debugging using libthread_db enabled]
[New Thread 0xb8028b00 (LWP 2186)]
[New Thread 0xb7fe5b90 (LWP 2189)]
[New Thread 0xb75e4b90 (LWP 2190)]
[New Thread 0xb6be3b90 (LWP 2191)]
redhat.com has address

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb7fe5b90 (LWP 2189)]
send_udp (query=0xffffffff) at dighost.c:2328
2328		l = query->lookup;
(gdb) p query
$1 = (dig_query_t *) 0xffffffff
Comment 1 Jakub Hrozek 2008-11-27 10:32:52 EST
Sorry, I also meant to show how the forwarding is configured:
forward         first;
forwarders      {; };
allow-query     { localhost;; };
Comment 2 Adam Tkac 2008-12-02 03:48:49 EST

*** This bug has been marked as a duplicate of bug 452060 ***

Note You need to log in before you can comment on or make changes to this bug.