Re: bug: open_process causes flickering

["John E. Davis" <davis@xxxxxxxxxxxxx>]

=?UTF-8?Q?J=C3=B6rg?= Sommer <joerg@xxxxxxxxxxxx> wrote:
>whatbuf();
>setbuf("output");
>variable pid = open_process("/bin/sleep", "4", 1);
>sw2buf( () );
>process_query_at_exit(pid, 1);
>set_process(pid, "output", "output");
>
>% strace -tt -o /tmp/xj.st xjed /tmp/test.sl -l /tmp/test.sl
>
>After the window poped up I must press a key, otherwise this does not
>show the effect I want to show. If it does not work, try it without strace.
>
>Can someone acknowledge that the cursor starts flickering?

I am unable to reproduce this using 0.99.19.

[...]
>20:28:22.360548 write(3, "M\1\0\5\3\200\0\4\3\200\0\5\0\0\0`\0s\0/", 20) = 20
>20:28:22.360720 select(4, [3], NULL, NULL, {0, 0}) = 0 (Timeout)
>20:28:22.360803 ioctl(3, FIONREAD, [0]) = 0
>20:28:22.360866 select(4, [3], NULL, NULL, {0, 0}) = 0 (Timeout)
>20:28:22.360982 write(3, "M\1\0\5\3\200\0\4\3\200\0\6\0\0\0`\0s\0/", 20) = 20
>20:28:22.361175 write(3,
>  "M\1\0\5\3\200\0\4\3\200\0\5\0\0\0`\0s\0/M\1\0\5\3\200\0"..., 40) = 40
>20:28:22.361366 ioctl(3, FIONREAD, [0]) = 0
>20:28:22.361436 select(6, [3 5], NULL, NULL, {45, 0}) = 1 (in [5], left {45, 0})
>20:28:22.361522 read(5, 0x7fae94a8, 512) = -1 EIO (Input/output error)
>20:28:22.361594 ioctl(3, FIONREAD, [0]) = 0
>20:28:22.361775 --- SIGCHLD (Child exited) @ 0 (0) ---
>
>I've put the whole strace log in http://www.minet.uni-jena.de/~joergs/xj.st

I am unable access this.

>I would say the select() is the one in line 537 in unix.c and the ioctl()
>is somewhere in the call of jed_insert_nbytes (buf, n) in line 979 in
>jprocess.c. I can't really see what goes wrong and where.

The ioctl uses 3 as the file descriptor, which is the one used to
communicate with X.  The call to select above is checking for input on
file-descriptors 3 and 5, where 5 denotes the subprocess.

--John

--------------------------
To unsubscribe send email to <jed-users-request@xxxxxxxxxxx> with
the word "unsubscribe" in the message body.
Need help? Email <jed-users-owner@xxxxxxxxxxx>.