public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pasky at suse dot cz" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/10071] 2.9.90 (2009-04-14) libio/genops.c : __underflow() does not handle NULL FP
Date: Wed, 15 Apr 2009 11:11:00 -0000	[thread overview]
Message-ID: <20090415111058.21270.qmail@sourceware.org> (raw)
In-Reply-To: <20090414185756.10071.jason.vas.dias@gmail.com>


------- Additional Comments From pasky at suse dot cz  2009-04-15 11:10 -------
Note that you might use the git mirror
(http://sources.redhat.com/glibc/wiki/GlibcGit) to quickly bisect glibc to see
exactly which commit broke it. (On the other hand, bisecting might be a bit of a
challenge since unfortunately, Ulrich usually does not commit change to multiple
files all at once but separately for each file, so many revisions might not
compile - but I'm not sure how big portion in practice, so it's something to try
and see.)

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=10071

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  parent reply	other threads:[~2009-04-15 11:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-14 18:58 [Bug libc/10071] New: " jason dot vas dot dias at gmail dot com
2009-04-14 19:01 ` [Bug libc/10071] " jason dot vas dot dias at gmail dot com
2009-04-14 19:08 ` drepper at redhat dot com
2009-04-15  0:14 ` jason dot vas dot dias at gmail dot com
2009-04-15 11:11 ` pasky at suse dot cz [this message]
2009-04-19  7:28 ` jason dot vas dot dias at gmail dot com
2009-04-19  8:46 ` jason dot vas dot dias at gmail dot com
     [not found] <bug-10071-131@http.sourceware.org/bugzilla/>
2014-07-01  7:07 ` fweimer at redhat 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=20090415111058.21270.qmail@sourceware.org \
    --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: link
Be 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).