home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   comp.sys.apple2      Discussion about Apple II micros      56,720 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 55,958 of 56,720   
   stephenheumann@gmail.com to justliketom...@gmail.com   
   Re: ORCA/C v2.10 v2.2.0 B6 Prizm debugge   
   09 Dec 22 13:10:22   
   
   From: stephen...@gmail.com   
      
   On Friday, December 9, 2022 at 7:40:33 AM UTC-6, justliketom...@gmail.com   
   wrote:   
   > Even simplest code setting a break point doesn't work for me:    
   >    
   > #include     
   >    
   > void main(void)    
   > {    
   > int i,x;    
   >    
   > printf("Say what? \n");    
   >    
   > for(i = 0; i < 11; i++)    
   > {    
   >    
   > x = i * 2;    
   > }    
   >    
   > printf("What do you mean?\n");    
   >    
   > }    
   > I'll place the cursor at the beginning of the line "x = I * 2;", set a   
   breakpoint, either from the debug menu or OA-H and try to trace through or   
   otherwise compile and I'll get a stop alert "undeclared identifier" . The   
   shell window points to x as an    
   undeclared identifier. It seems the breakpoint is set as a ^D. If I don't set   
   a breakpoint and just select step from the debug menu I can step through the   
   code and display variables in the variable window as expected.    
      
   I tried doing the same thing with the exact code that you posted, and I'm   
   still not seeing the problem. One thing to check is to make sure that there   
   isn't actually an undeclared identifier. If the line is actually "x = I * 2;"   
   with a capital I, then    
   that would be an undeclared identifier, since C is case-sensitive. If that's   
   not the issue, then I suspect it's some problem with your setup.   
      
   > I'm not sure what I have wrong. I was thinking that updating v2.1.0 to   
   v2.2.0 B6 doesn't overwrite everything and leaves some old stuff untouched and   
   that is where the problem lies but I'm not sure that is so.   
      
   It's true that the ORCA/C 2.2.0 B6 update does not overwrite everything, so if   
   there was some problem with your ORCA installation, it might still exist. I'd   
   suggest making a copy of the stock ORCA installation from Opus ][, applying   
   the ORCA/C 2.2.0 B6    
   update on top of that, and seeing if you still have the issue there. If not,   
   it was likely a problem with your old installation.   
      
   --    
   Stephen Heumann   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca