Re: libg++-2.3 strange bug

Article View: gnu.g++.lib.bug

Article #345

#345

From: bothner
Date: Wed, 30 Dec 1992 10:50

14 lines
982 bytes

> Just noticed a strange bug when redirecting libg++ 2.3 iostream
> output to a pipe: OUTPUT GETS LOST!

The problem is the fseek in stdiobuf::sync() (in stdiostream.C).
I'm not sure what the right fix is.  One possibility is to just
remove the call.  That isn't quite right, but it may be close enough.
Another possibilty is to do the fseek(), but ignore the result.

> just trying to figure out how to debug such a thing. ;-)

I did it by using a named pipe.

	--Per Bothner
Cygnus Support     bothner@cygnus.com

Technical Details

Message-ID: <9212310250.AA13642@cygnus.com>

Path: arc1-ca.pugleaf.net!sparky!uunet!wupost!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!cygnus.com!bothner

References: <1992Dec29.170317.20721@dfv.rwth-aachen.de>

Show Full Headers

Complete Article Headers

Newsgroups: gnu.g++.lib.bug
Path: arc1-ca.pugleaf.net!sparky!uunet!wupost!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!cygnus.com!bothner
From: bothner@cygnus.com
Subject: Re: libg++-2.3 strange bug
Message-ID: <9212310250.AA13642@cygnus.com>
Sender: gnulists@ai.mit.edu
Organization: GNUs Not Usenet
References: <1992Dec29.170317.20721@dfv.rwth-aachen.de>
Distribution: gnu
Date: Wed, 30 Dec 1992 10:50:32 GMT
Approved: bug-lib-g++@prep.ai.mit.edu
Lines: 15

Reply to Parent Message