Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watmath!clyde!rutgers!husc6!seismo!rochester!pt.cs.cmu.edu!ius2.cs.cmu.edu!edw From: edw@ius2.cs.cmu.edu.UUCP Newsgroups: comp.unix.questions Subject: Re: 4.3BSD dbx question: internal error? Message-ID: <1085@ius2.cs.cmu.edu> Date: Sat, 4-Apr-87 17:00:36 EST Article-I.D.: ius2.1085 Posted: Sat Apr 4 17:00:36 1987 Date-Received: Sat, 18-Apr-87 02:23:10 EST References: <1331@uwmacc.UUCP> Organization: Carnegie-Mellon University, CS/RI Lines: 49 Keywords: dbx unix 4.3bsd microvax > Another curiosity is that when I said, for example, "trace dnum" > to follow a variable "dnum" it said "dnum is not defined" when in > fact dnum was declared right in the main program. > > What can cause variables not to be seen by dbx? > -- > Jeff Percival (jwp@salvax1) The current scope, which can be set using func . Also, I believe that variables declared in main can not be seen by any other subroutines, hence if you did a trace on a variable declared in main and current referrence frame was some other subroutine call then a var blank not active or defined message would appear. Here's a few problems I have had with suns dbx. 1) When I try to print out a variable which is defined and within the current scope, I get the error message: syntax error on " pose" the command I'm using is "print pose" - no quotes. 2) When tracing down a seg fault related to malloc memory problems, I typed the command : call malloc_verify(2) A seconds later, I get the error message : Coprocessor protocol error ..... Syncing disk And of course the sun precedes to reboot itself. The bugs that I was looking for are now fix, I just thought I'd share some related problems. -- Eddie Wyatt Those who know what's best for us- Must rise and save us from ourselves Quick to judge ... Quick to anger ... Slow to understand... Ignorance and prejudice and fear [all] Walk hand in hand. - RUSH