gnuplot-beta

x11 prints garbage to stdout on OS/2

[Petr M. <mi...@ph...>]

There is a report, which I can confirm, that X11 terminal under OS/2

- prints a lot of garbage onto the gnuplot xterm, or
- blocks until you hit <Enter>

In the latter case, gnuplot continues to plot OK.

I *guess* there is some code using PIPE_IPC without #ifdef PIPE_IPC around
it, and thus all the communication goes into the screen. Or reading stdin
where it should not, or like that. Can somebody have a look to this issue?
Thanks. I haven't found a problem in gplt_x11.c, maybe somewhere else?

(Note: OS/2 communication is surrounded by OS2_IPC)

---
Petr Mikulik

Re: x11 prints garbage to stdout on OS/2

[Ethan M. <merritt@u.washington.edu>]

On Tuesday 16 December 2003 06:52, Petr Mikulik wrote:
> There is a report, which I can confirm, that X11 terminal under OS/2
>
> - prints a lot of garbage onto the gnuplot xterm, or

I have no idea about this one, and no way of debugging it.
Could you at least establish whether it is gnuplot or gnuplot_x11
that produces this garbage?

> I *guess* there is some code using PIPE_IPC without #ifdef PIPE_IPC
> around it, and thus all the communication goes into the screen.

I don't think so, at least not in the x11 code.  This would cause a
severe error when the program tried to write to an invalid file descripto=
r.

--=20
Ethan A Merritt       merritt@u.washington.edu
Biomolecular Structure Center Box 357742
University of Washington, Seattle, WA 98195

Re: x11 prints garbage to stdout on OS/2

[Ethan M. <merritt@u.washington.edu>]

[ resending this message with (I hope) correct character encoding ]

On Tuesday 16 December 2003 08:24, Petr Mikulik wrote:
> Franz has found the patch which started to cause this problem.
> Ethan, can you please look at it?

I have no way of debugging anything under os2.
So unless you can find a similar failure that I can reproduce here,
I can't do much other than maybe disable the feedback altogether
with a command line option (see other message).

>
> 20. June 2003 works  and  21. June 2003 doesn't.
> So one of these patches are the culprit:
> From Changelog:
>
> 2003-06-20  Ethan Merritt  <merritt@u.washington.edu>
> 2003-06-19  Ethan Merritt  <merritt@u.washington.edu>

The details of this code were changed by later patches,
so this only point a finger at the entire feedback mechanism
for requesting font and sizing information.=20
My proposed non-fix remains to add a command line
option disabling this feedback mechanism.

--=20
Ethan A Merritt       merritt@u.washington.edu
Biomolecular Structure Center Box 357742
University of Washington, Seattle, WA 98195

Re: x11 prints garbage to stdout on OS/2

[Ethan M. <merritt@u.washington.edu>]

On Tuesday 16 December 2003 10:34, Ethan Merritt wrote:
> My proposed non-fix remains to add a command line
> option disabling this feedback mechanism.

I have added a command line option
=09gnuplot -nofeedback
that disables the feedback path which is causing problems.
This is not an ideal fix, just a work-around.
There is a corresponding XResource:
=09gnuplot*feedback:=09off                 (or false)

Please let me know if this successfully bypasses the=20
symptoms you saw under os2.  As a bonus it should=20
also allow the earlier "lost characters" problem we saw
for awk scripts.

If this works, I will add suitable documentation for it.
We can chip away at  fixing the underlying problem later.

--=20
Ethan A Merritt       merritt@u.washington.edu
Biomolecular Structure Center Box 357742
University of Washington, Seattle, WA 98195

Re: x11 prints garbage to stdout on OS/2

[Ethan M. <merritt@u.washington.edu>]

[ resending the message with hopefully correct character encoding ]

On Tuesday 16 December 2003 06:52, Petr Mikulik wrote:
> There is a report, which I can confirm, that X11 terminal under OS/2
>
> - prints a lot of garbage onto the gnuplot xterm, or

I have no idea about this one, and no way of debugging it.
Could you at least establish whether it is gnuplot or gnuplot_x11
that produces this garbage?

> I *guess* there is some code using PIPE_IPC without #ifdef PIPE_IPC
> around it, and thus all the communication goes into the screen.

I don't think so, at least not in the x11.trm code.  This would cause a
severe error when the program tried to write to an invalid file descripto=
r.


--=20
Ethan A Merritt       merritt@u.washington.edu
Biomolecular Structure Center Box 357742
University of Washington, Seattle, WA 98195