kxd bug?

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

kxd bug?

Harald Barth

1. Log in with rxtelnet
2. You get an X11 socket (say :4.0) on the remote end.
3. Start an X11 program (say xlogo&) - fine
4. Start another X11 program (say xlogo&) - fine
5. Kill one of the xlogo above.
6. Start one more X11 program (say xlogo&) - meep,
   something broke when killing the process in 5.

haba@habitat haba $ xlogo &
[2] 13517
haba@habitat haba $ xlogo &
[3] 13519
haba@habitat haba $ kill %3
haba@habitat haba $ xlogo &
[4] 13521
[3]   Terminated              xlogo
haba@habitat haba $ Error: Can't open display: :4.0

[4]+  Exit 1                  xlogo
haba@habitat haba $

This is under Linux x86 (gentoo).

 $ ./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --enable-shared --enable-static --prefix=/usr/heimdal-0.7 CFLAGS=-march=i686 -msse -mmmx -mfpmath=sse,387 -Os -pipe -fomit-frame-pointer -g LDFLAGS=

This works with my old 0.6.4 kxd, but that can be compiled
with slightly differnt flags etc.
(kx at other end does not seem to matter).

Let me know if you need help to recreate the bug.


PS: I'm in a maze of twitsy litte functions, all named "doit_something" ;-)
my guess is that somewhere around the fork in doit_passive() something
that should be open is closed.