pphillip@cs.ubc.ca (Peter Phillips) (10/11/90)
The recent postings about "unkillable processes" reminded me of something I've see on DN3000/DN3500s running Domain/OS 10.2 involving dbx. It seems that giving dbx a non-object file causes it to hang and become an unkillable process. Like this: % dbx dbx version SR10.2(4) of 9/11/89 16:46 (apollo) enter object file name (default is a.out): foo.c After that dbx is unkillable, ignoring even a "sigp -blast". Yeah, I know, "Doc, my arm hurts when I do this", "Well, don't do that." but in a lab full of students you'll find someone twisting their arm behind their back or feeding "prog1.c" to dbx every once and a while. (Regardless of messages on the blackboard. A case of "Don't put beans in your ears..."?) Is this a known bug that someone has APR'ed? Or is it some sort of configuration problem? Why should dbx get so confused? Is it mapping in the object file and using an extra thread? Inquiring minds... -- Peter Phillips | Just because some of us can read and write <pphillip@cs.ubc.ca> | and do a little math, that doesn't mean we UBC Computer Science | deserve to conquer the Universe. - E.D.Hartke