Thread View: gnu.gcc.bug
1 messages
1 total messages
Started by Mike Stump
Sat, 29 Aug 1992 14:25
Re: bug with iostream.h?
Author: Mike Stump
Date: Sat, 29 Aug 1992 14:25
Date: Sat, 29 Aug 1992 14:25
37 lines
1630 bytes
1630 bytes
I suspect this is a problem with libg++. You need to report bugs or problems in libg++ to the bug-lib-g++@prep.ai.mit.edu list. libg++-2.2 I believe corrects these problems. > Date: Thu, 23 Jul 92 00:14:29 +0100 > From: jb145@eng.cam.ac.uk > Message-Id: <9207222314.AA27182@caxton> > To: bug-gcc@prep.ai.mit.edu > #I've been having a very frustrating problem with iostream.h in gcc > version 2.0(?). I am running g++ on a Decstation mips machine. > Is there any known bug in the compiler with respect to buffered input > int from; cin >> from; > then the program runs fine, looping forever without keyboard input. > But when the line is left in, then it works fine for about 100 or 200 > inputs cycles until suddenly crashing with a message like: > grow failed because stack limit exceeded, pid 26935, proc play > ts = 0x1c, ds = 0x1d, ss = 0x80 > Segmentation fault (core dumped) > I have been chasing this problem for over two weeks and am hoping, > begging that you will have a clue what might be causing it. By the > way, I've tried lots of hacks such as replacing > cin >> from; > with > char str[5]; cin >> str; from = atoi(str); > but the crash remains despite all my efforts.
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads