Disclose-Recipients: prohibited
Date: Wed, 1 Mar 1995 15:27:34 EST
From: "Steve Salter (519) 452-4447" <SALTERS AT AM DOT FANSHAWEC DOT ON DOT CA>
Subject: Re: Problems with simple fstream program
To: DJGPP Mailing List <djgpp AT sun DOT soe DOT clarkson DOT edu>
Autoforwarded: false
Importance: normal
Ua-Content-Id: 11930BDB2000
Hop-Count: 0

I said:

> 
> I got and compiled the libiostream library for debugging and followed the
call
> to infile.get(one_char).  Unfortunately, the error occurred in a deeply
buried
> function which I didn't trace into (the function call is "_strbuf->sbumpc()".

> This translates into a call to _IO_getc(this).
 
I have since discovered that the problem seems to be in the way that the file
is opened.  I think, without proof, that it is being opened with some attribute
like NO_READ + NO_WRITE.

DJ said:
> In general, if you have access to a Unix machine and can test the same
> program on the unix version of gcc/libgcc and it fails there also,
> it's a gnu bug.  If it runs on the unix platform, it's a djgpp bug.
> If you can't test it on a unix platform, you're on your own for
> figuring it out - that's what the sources are for.
>
> Or, you mail to the list and hope someone else knows.

I have no access to a Unix machine.  Could someone with access to one please
compile and test the original program (my guess is that it will create the
files COPY and PRN, rather than printing one, but that's tangential to the
problem, I believe).  I can mail a copy of the test program, if necessary.

Thanks,

Steve Salter
Programmer, Fanshawe College
London, ON Canada
salters AT admin DOT fanshawec DOT on DOT ca