jwp@uwmacc.UUCP (04/04/87)
I was using dbx on a 4.3BSD MicroVAX II, like this: dbx a.out (dbx) trace when it said (approximately) "internal error, reference through nil pointer at line 119 in languages.c" and aborted the dbx session, leaving me back with my csh prompt. What can cause such a thing? 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)
edw@ius2.cs.cmu.edu.UUCP (04/05/87)
> 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 <funcname>. 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