On Thu, 2002-12-05 at 13:03, Dragan Stancevic wrote:
I haven't had a chance to toy around with the problem much but as I describe in the article one way to mitigate that problem is to run a "ps" on your system when kylix freezes. Than attach with "strace -p" to the only kylix process that is in a R state. Than watch kylix come back to life. I reported
I also have Kylix 3 OE installed on SuSE 8.1 and I have the same problem as Hahnsson. Unfortunately this method of reviving Kylix does not work for me. When I do ps -efl | grep kylix, none of the processes are in the 'R' state. andre@obelix:/usr/local/bin> ps -efl | grep kylix 000 S andre 1881 1860 2 85 0 - 18073 rt_sig 08:57 ? 00:00:02 /usr/local/kylix3/bin/bcblin 002 S andre 1884 1881 0 75 0 - 18073 schedu 08:57 ? 00:00:00 /usr/local/kylix3/bin/bcblin 002 S andre 1885 1884 9 75 0 - 18073 schedu 08:57 ? 00:00:10 /usr/local/kylix3/bin/bcblin 002 S andre 1886 1884 0 75 0 - 18073 schedu 08:57 ? 00:00:00 /usr/local/kylix3/bin/bcblin 002 S andre 1887 1884 0 75 0 - 18073 schedu 08:57 ? 00:00:00 /usr/local/kylix3/bin/bcblin 002 S andre 1888 1884 0 75 0 - 18073 schedu 08:58 ? 00:00:00 /usr/local/kylix3/bin/bcblin 000 S andre 1931 1749 0 80 0 - 406 pipe_w 08:59 pts/2 00:00:00 grep kylix I tried strace on all of the processes, but none of them have any effect on Kylix. Has anybody had better luck? Any feedback from Borland? -- Andre Truter Software Engineer Registered Linux user #185282 ICQ #40935899 AIM: trusoftzaf http://www.trusoft.za.net <-------------------------------------------------> < The box said: Requires Windows 95 or better... > < So I installed Linux > <------------------------------------------------->