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,956 of 56,720   
   Tom Thumb to stephen...@gmail.com   
   Re: ORCA/C v2.10 v2.2.0 B6 Prizm debugge   
   08 Dec 22 20:37:11   
   
   From: justliketomsthumbsblues@gmail.com   
      
   On Thursday, December 8, 2022 at 5:50:01 PM UTC-5, stephen...@gmail.com wrote:   
   > On Thursday, December 8, 2022 at 12:23:00 PM UTC-6, justliketom...@gmail.com   
   wrote:    
   > > Since upgrading ORCA/C 2.1.0 to 2.2.0 B6 I’m unable to enter the   
   debugger using Prizm. If I set a breakpoint and try to run or compile I get an   
   undeclared identifier error where the breakpoint is set.    
   > >    
   > > Is this a known thing or is there something I haven’t done that I   
   should? It seems to work using v2.1.0 though I’m having some difficulty   
   using it with a desktop exe.    
   > >    
   > > Unsetting a breakpoint doesn’t work in either version though I’ll be   
   the first to admit I have no experience with it.    
   > >    
   > > So, deal with it and use v2.2.0 B6 or revert to v2.1.0 or…?   
   > This sounds like it could be a bug in ORCA/C 2.2.0 B6, but it is not one I'm   
   aware of, and in a couple quick tests I could not reproduce it. I was able to   
   set breakpoints in Prizm, build a small program without errors, and debug it   
   using Prizm with    
   ORCA/C 2.2.0 B6.    
   >    
   > If you can provide more details, like an example program that has the   
   problem and where exactly you're setting a breakpoint in it, I'd be happy to   
   look into it more.    
   >    
   > --    
   > Stephen Heumann   
      
    Oh, so it works for you. Thank you for verifying that. I'm inclined to   
   believe my install is suspect. It's all based on a years old install on my   
   IIgs. It seems to me there are other troubles. I think my best course of   
   action is a fresh install. Ah,    
   where to start...   
      
   Curious; compiling from the  shell the executable's subtype is $0100 and runs   
   invoked from the shell. Compiling in Prizm the executable's subtype is $DB01.   
   That will run in Prizm's shell window but will crash from the text shell. Is   
   that what is?   
      
   --- 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