Re: `print' does not print

[Eli Zaretskii]

> Date: Fri, 22 Mar 2002 15:22:25 +0100
> From: Ralf Fassel <ralfixx@gmx.de>
> 
> This is `par' on IRIX, which shows close(4) and close(5), but no (!)
> write:

This gets stranger and stranger...

> If I compile print.c alone with cc, and all the rest with gcc, I see
>   ...
>   575mS                 : open("/disk4/tmp/ralf/Software/emacs-21.2/foo", 
> O_RDONLY, 0) = 5
>   575mS                 : close(5) OK
>   576mS                 : open("/disk4/tmp/ralf/Software/emacs-21.2/foo", 
> O_RDONLY, 0) = 5
>   576mS                 : close(5) OK
>   578mS                 : open("/disk4/tmp/ralf/Software/emacs-21.2/foo", 
> O_RDONLY, 0) = 5
>   581mS                 : close(5) OK
>   587mS                 : write(1, "\n", 1) = 1
>   603mS                 : write(1, ""21.2.3"\n", 9) = 9
> finish
> 
> The CPP-preprocessed print.c shows the `fwrite' call in both cases,

How about disassembly of printchar?  Does it show the call to fwrite
in both cases?

> So the calls via gdb seem to work, while the calls from emacs itself
> don't.  I do not understand this at all.

Very strange, indeed...

What happens if you replace `fwrite' with `fflush' followed by
`write'?  Does that change anything?

Another idea is to put a breakpoint inside fwrite, and see if it's
called at all.