Dan, I've seen something similar with very same port.status options where PORT.STATUS seemed to cause other uv telnet sessions to drop.. Maybe UV10.0 or earlier. I'm still not clear on whether you are ud or uv.
It was during my most intensive use of the command ever. I did not pursue the bug, so I do not know exactly what part of port.status caused exactly what problem, or whether [pid] or CALL.STACK were really implicated. I just stopped using it so intensively. My guess was that there was/is some sort of latent bug where the offending code probably it needs to be executed in synch with something happening on the affected other port. The likelihood of the bug being activated is probably low, but if I did it often enough, I'd get (seemingly random) hits. That's as far as I took it and moved on. Dan, I for one would appreciate it if you would report back anything you learn. Regards, Chuck On Mon, Dec 7, 2009 at 6:06 PM, Dan McGrath <dmc...@imb.com.au> wrote: > Hi all, just wondering if anyone has encountered this before? > > I was running some tests and discovered that doing a "PORT.STATUS PID > pid CALL.STACK" on a program that is waiting to open a named pipe with > OSOPEN caused it to bomb out. > _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
