public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
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 [thread overview] Message-ID: <bug-17630-131-ZbM0uyevRn@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-17630-131@http.sourceware.org/bugzilla/> 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.
next prev parent reply other threads:[~2014-11-24 16:29 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-20 13:44 [Bug network/17630] New: " yashavanth.hsn at gmail dot com 2014-11-20 14:47 ` [Bug network/17630] " schwab@linux-m68k.org 2014-11-24 16:29 ` yashavanth.hsn at gmail dot com [this message] 2014-11-24 16:31 ` yashavanth.hsn at gmail dot com 2014-11-24 16:58 ` schwab@linux-m68k.org 2014-11-25 9:48 ` yashavanth.hsn at gmail dot com 2014-12-09 13:34 ` schwab@linux-m68k.org 2014-12-12 14:06 ` fweimer at redhat dot com 2014-12-15 9:26 ` yashavanth.hsn at gmail dot com 2014-12-15 9:34 ` schwab@linux-m68k.org 2014-12-15 9:50 ` yashavanth.hsn at gmail dot com 2014-12-15 9:50 ` fweimer at redhat dot com 2014-12-16 9:10 ` cvs-commit at gcc dot gnu.org 2014-12-16 9:11 ` fweimer at redhat dot com 2014-12-18 1:07 ` cvs-commit at gcc dot gnu.org 2014-12-18 6:17 ` [Bug network/17630] endless loop in getaddr_r (CVE-2014-9402) fweimer at redhat dot com 2015-01-14 12:19 ` cvs-commit at gcc dot gnu.org 2015-01-14 13:13 ` cvs-commit at gcc dot gnu.org 2015-01-16 16:59 ` cvs-commit at gcc dot gnu.org 2015-01-16 17:02 ` cvs-commit at gcc dot gnu.org 2015-01-16 17:03 ` cvs-commit at gcc dot gnu.org 2015-01-21 13:56 ` cvs-commit at gcc dot gnu.org 2015-01-29 18:50 ` cvs-commit at gcc dot gnu.org 2015-02-12 13:05 ` cvs-commit at gcc dot gnu.org 2015-02-23 14:06 ` cvs-commit at gcc dot gnu.org 2015-02-23 14:23 ` cvs-commit at gcc dot gnu.org 2015-02-23 15:02 ` cvs-commit at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-17630-131-ZbM0uyevRn@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).