wileyjm@cs.rpi.edu (John-Michael Wiley) (02/05/91)
I have an XClient who sits with an unmapped window and awaits messages. When it gets a specific messages it maps the windows and goes on. The problem occurrs if someone turns off the terminal (Xterm) while the client is running. If the client is in the wait loop it is fine. An XSync upon restarting is takes care of everything. However if the client is in the middle of starting up or if the client has a window on the screen, it does not die. Then when it tries to do something like change some values or map a window it dies. Does anyone have a solution to this problem. -- J.M. Wiley ------ wileyjm@turing.cs.rpi.edu Go Heels'
wileyjm@turing.cs.rpi.edu (John-Michael Wiley) (02/05/91)
In article <Z2%&09&@rpi.edu> wileyjm@cs.rpi.edu (John-Michael Wiley) writes: I have an XClient who sits with an unmapped window and awaits messages. When it gets a specific messages it maps the windows and goes on. The problem occurrs if someone turns off the terminal (Xterm) while the client is running. If the client is in the wait loop it is fine. An XSync upon restarting is takes care of everything. However if the client is in the middle of starting up or if the client has a window > on the screen, it does not die. Then when it tries to do something > like change some values or map a window it dies. Does anyone have a > solution to this problem. Sorry, that last statement should read, when it tries to do somehting like change window values or map a window it hangs. It also starts grabbing memory like mad. At the rate of about 100bytes/second, if that is any help. I would like the client to always die. I really don't care if it dies right away. As long as it dies and does not hang. -- J.M. Wiley ------ wileyjm@turing.cs.rpi.edu Go Heels'