From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <glibc-bugs-return-26686-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Received: (qmail 27516 invoked by alias); 24 Nov 2014 16:29:10 -0000
Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <glibc-bugs.sourceware.org>
List-Subscribe: <mailto:glibc-bugs-subscribe@sourceware.org>
List-Post: <mailto:glibc-bugs@sourceware.org>
List-Help: <mailto:glibc-bugs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: glibc-bugs-owner@sourceware.org
Received: (qmail 27012 invoked by uid 48); 24 Nov 2014 16:29:04 -0000
From: "yashavanth.hsn at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug network/17630] endless loop in getaddr_r
Date: Mon, 24 Nov 2014 16:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: network
X-Bugzilla-Version: 2.11
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: yashavanth.hsn at gmail dot com
X-Bugzilla-Status: WAITING
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-17630-131-ZbM0uyevRn@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-17630-131@http.sourceware.org/bugzilla/>
References: <bug-17630-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-11/txt/msg00178.txt.bz2

https://sourceware.org/bugzilla/show_bug.cgi?id=17630

--- Comment #2 from yashavanth.hsn at gmail dot com ---
This is the backtrace of the process when attached to gdb. 

it gives more information than requested.

#0  0x55751497 in getanswer_r (answer=0xffb4a260, anslen=<optimized out>,
result=0x55732e90 <resbuf.9301>, 
    buffer=0x89eec08 "\310\354\236\b", buflen=1024, errnop=0x55739688,
h_errnop=0xffb4a704, net_i=BYNAME)
    at nss_dns/dns-network.c:440
#1  0x55751aa0 in _nss_dns_getnetbyname_r (name=0xffb4a798
"passthrough.fw-notify.net", 
    result=0x55732e90 <resbuf.9301>, buffer=0x89eec08 "\310\354\236\b",
buflen=1024, errnop=0x55739688, 
    herrnop=0xffb4a704) at nss_dns/dns-network.c:146
#2  0x556b8993 in __getnetbyname_r (name=0xffb4a798
"passthrough.fw-notify.net", resbuf=0x55732e90 <resbuf.9301>, 
    buffer=0x89eec08 "\310\354\236\b", buflen=1024, result=0xffb4a708,
h_errnop=0xffb4a704)
    at ../nss/getXXbyYY_r.c:253
#3  0x556b83fe in getnetbyname (name=0xffb4a798 "passthrough.fw-notify.net") at
../nss/getXXbyYY.c:116
#4  0x55594c30 in network_to_ipaddr (name=<optimized out>) at xtables.c:1320
#5  ipparse_hostnetwork (name=0xffb4a798 "passthrough.fw-notify.net",
naddrs=0xffb4a794) at xtables.c:1359
#6  0x55594ec5 in xtables_ipparse_multiple (name=0x89ee4e0
"passthrough.fw-notify.net/32", addrpp=0xffb4aa08, 
    maskpp=0xffb4aa04, naddrs=0xffb4aa14) at xtables.c:1446
#7  0x0804fb8c in do_command4 (argc=9, argv=0x80a45e0 <newargv>,
table=0x80a45e8 <newargv+8>, handle=0xffb4ab6c)
    at iptables.c:1705
#8  0x0804d08c in iptables_restore_main (argc=2, argv=0xffb4d864) at
iptables-restore.c:440
#9  0x0804a7ca in main (argc=<error reading variable: Cannot access memory at
address 0x2e>, 
    argv=<error reading variable: Cannot access memory at address 0x32>) at
xtables-multi.c:40

Best Regards,
Yash

-- 
You are receiving this mail because:
You are on the CC list for the bug.