freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Re: Bug in read.c

From: martin dempsey <mjd AT digitaleveryware.com>
To: TDS Development Group <freetds AT franklin.oit.unc.edu>
Subject: Re: Bug in read.c
Date: 23 May 2002 07:59:55 -0700

> There appears to be an error in read.c that bit me the other day. I got a
> call from the Unix police saying that my processes were eating all of the
> CPU. I connected to them with gdb and found that they appeared to be stuck
> in a read() loop. There had been a network outage and my programs'
> connections to their db servers had been dropped, apparently precipitating
> the problem.

I've seen these same symptoms (cpu to 100% after a network problem) as
well.

Bug in read.c, SMASKELL, 05/23/2002
- <Possible follow-up(s)>
- Re: Bug in read.c, martin dempsey, 05/23/2002
- Re: Bug in read.c, Jon Pounder, 05/23/2002
- Re: Bug in read.c, SMASKELL, 05/23/2002
- RE: Bug in read.c, Matt Kynaston, 05/27/2002
- Re: Bug in read.c, ZIGLIO Frediano, 05/27/2002