This is the mail archive of the libc-hacker@sourceware.cygnus.com mailing list for the glibc project.

Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: Bugs in glibc 2.2

To: "H . J . Lu" <hjl at lucon dot org>
Subject: Re: Bugs in glibc 2.2
From: Jakub Jelinek <jakub at redhat dot com>
Date: Sun, 21 May 2000 14:44:41 +0200
Cc: GNU C Library <libc-hacker at sourceware dot cygnus dot com>
References: <20000520164618.A840@lucon.org> <20000521063407.V474@sunsite.ms.mff.cuni.cz> <20000520221616.A1857@lucon.org>
Reply-To: Jakub Jelinek <jakub at redhat dot com>

On Sat, May 20, 2000 at 10:16:16PM -0700, H . J . Lu wrote:
> On Sun, May 21, 2000 at 06:34:07AM +0200, Jakub Jelinek wrote:
> > > when 0 may be a valid fd for something else. There are other
> > > bugs I am trying to do down. For example,
> > > 
> > > # man read 
> > > 
> > > no longer works.
> > 
> > I'm working on a fix for this now if it is groff segfaulting.
> 
> It seems like the groff bug. But I can be wrong.

See my other mail.

> BTW, I put
> glibc 2.2 on RedHat 6.2. It doesn't work every well. I will
> try to fix the resolver bug.

What other issues do you see?
I'm aware at the moment only about some rcmd issues and
different resolver behaviour (need to investigate this still).

	Jakub

Follow-Ups:
- Re: Bugs in glibc 2.2
  - From: H . J . Lu

References:
- Bugs in glibc 2.2
  - From: H . J . Lu
- Re: Bugs in glibc 2.2
  - From: Jakub Jelinek
- Re: Bugs in glibc 2.2
  - From: H . J . Lu

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]