Re: bug report

[Mathew Yeates]

I get the same result using groff-current.

Something really strange.... my system trace shows that
man closes file descriptors 0,1, and 2 just prior to execv-ing nroff.
Maybe the problem here is SGI's "man"?? I notice that when I run
using the sgi nroff, eqn does not write to stdout. Instead, nothing
is written to stdout again until man does a "write" after
calling ioctl(1, __OLD_TCGETA, <bad indirect __old_termio param - len 30>) OK

Maybe it isnt safe to call printf from with eqn without checking first
that the IO file handles are still open??

Mathew

> > Error: geqn fails when it tries to write output to stdout.
> 
> I can't reproduce this on my Linux box.  Please download the current
> development version from
> 
>   ftp://ftp.ffii.org/pub/groff/devel/groff-current.tar.gz
> 
> to check whether this error still happens.
> 
> > Doing a system call trace, it appears that stdout has been closed. I
> > added a line of code to print out the errno when the printf fails. I
> > get "stdout': Bad file number"
> > 
> > It appears that stdout was closed long before the error. In the
> > trace I see "open" calls returning the value 1.
> 
> I've never received such an error report -- what about a different
> version of g++?  What about the native IRIX compiler?
> 
> 
>     Werner