tony@xios.UUCP (Keeper Of News) (09/03/86)
Machine/software: Ultrix 1.2 running on a microVax II, GNU emacs 17.54 Scenario: A user logs in, runs emacs, and puts it in the background. Runs dbx, and at some point gets into a state where he can't advance past a breakpoint. That is, he sets a breakpoint, runs the program, gets to the breakpoint, types continue, and dbx prints out the line again, but doesn't execute any instructions in the program being debugged. This behaviour can be worked around by deleting the breakpoint, single stepping, and setting the breakpoint again. The interesting thing is that this behaviour now continues for new invocations of dbx. That is, you can quit dbx, fire up another one on a totally different program, and get the same behaviour. This can only be cleared by logging out and logging in again. This happens at apparently random times, but it seems to require emacs having been run. That is, this behaviour does not occur if we run vi instead of emacs. If I didn't know better I'd say that either emacs or dbx is mucking about with the parent shell's environment somehow (1/2 :-). Has anyone ever heard of anything like this? Any help would be greatly appreciated. -- ------------------------------------------------------------------------------- Tony Lill Keeper of News @ Xios Systems Corporation 1600 Carling Avenue, Suite 150, Ottawa, Ontario, Canada, K1Z 8R8 (613) 725-5411 xios!tony ------------------------------------------------------------------------------- Not the edge of the world, but we can see it from here.