public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "drepper.fsp at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/10484] getaddrinfo segfaults if /etc/hosts has a long line Date: Thu, 13 Jan 2011 16:29:00 -0000 [thread overview] Message-ID: <bug-10484-131-St0RCJ8PGL@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-10484-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=10484 Ulrich Drepper <drepper.fsp at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #5 from Ulrich Drepper <drepper.fsp at gmail dot com> 2011-01-13 16:29:25 UTC --- I've checked in a patch. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next prev parent reply other threads:[~2011-01-13 16:29 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-10484-131@http.sourceware.org/bugzilla/> 2011-01-07 17:41 ` agl at imperialviolet dot org 2011-01-07 18:04 ` agl at imperialviolet dot org 2011-01-13 16:29 ` drepper.fsp at gmail dot com [this message] 2014-02-16 18:29 ` jackie.rosen at hushmail dot com 2014-05-28 19:46 ` schwab at sourceware dot org 2014-07-01 7:26 ` fweimer at redhat dot com 2009-08-05 15:22 [Bug libc/10484] New: " lars at ubuntu dot com 2009-08-05 19:29 ` [Bug libc/10484] " fibonacci dot prower at gmail dot com 2009-10-30 5:38 ` drepper at redhat dot com 2009-10-30 13:49 ` fibonacci dot prower at gmail dot com 2009-11-17 7:02 ` fibonacci dot prower at gmail dot com
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-10484-131-St0RCJ8PGL@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /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).