It crashes on my old Quadra 660 sys 7.5 and my PowerMac 7200 system 8.1
Both the 8.0x and the 7.0x versions crash.
I tried booting with all extensions off and still no luck.
I know that I had no problems using my ancient LC III System 7.0 way back
when using Symantec 7.0
- Robert
I'm running Symantec C 7.0 and its debugger on a PowerMac 8500 and OS
8.1, without any problems. However, I've found that the debugger
crashes upon quitting when running on OS 8.5. This has motivated me to
(finally) look into updating my development environment. I am
considering moving to CodeWarrior but if there's an acceptable new
version of Symantec, that would probably save me some time. Please let
me know if you find out anything relevant to this.
Thanks.
David
----------------------------------------------------
(to reply, delete "no.spam." from my return address)
Try rebuilding the project file from scratch (i.e. a new empty
project then add all your files and libraries). I've had a similar
problem using version 6.0, and it seems to be a result of a partially
corrupted project file - everything works fine until you try and
run the debugger on certain heavily-edited source files. If I know
that the crash only happens when executing code in a particular source
file, I'll often simply remove/add the file (NOT just turn debugging
off/on), and that seems to fix it.
David Stone
(remove the obvious bits to reply...)
This posting does not constitute agreement on my part to have my email
address added to ANY mailing lists or to receive "one time" mailings of
a bulk or commercial nature.
I have experienced the same problem on a Performa 5200. SC++ 8.0 gives an error
message (some -25xxx for which I never could figure out the meaning) when I try
to start the debugger. Installing all Updates (8.0.3) did not help.
Just before Symantec ceased to support this product, I found out, they had announced
a "Release 5" free of charge but my local representative was not willing to recognize
this and tried to sell me a new version...
I am still using the buggy version without using the Debugger - and
astonishinly it
works rather well :-). I have had some thought on moving to CW - but they are
too expensive
for a switch.
HNS
BTW: THINK C 7.0 worked fine.
> Robert Gulledge wrote:
> >
> > I'm stuck using Symantec's compiler for now and I can't figure out why the
> > debugger crashes whenever I try and run any project using the debugger.
I too am plagued with problems generating code as well as occaisional
compiler crashes - using Think 7.0.4 project manager with v8 compilers
under OS 7.5.5. Am now switching to MW CW Pro-4, and am porting TCL 2.0.9
in the process, look for it on the TCL ftp site in a couple weeks, should
be an anouncement here as well (2.0.8 is already ported to Pro-4 and is
posted there now).
The v7 project manager is fragile and corrupts its project file easily,
you have to be ready with 'spares' (strip object code from a finder copy
of the project file and make an archive copy of it and your source code
periodically).
you might also consider what software installs you have done recently, it
is remotely conceivable that some changed library in your system folder
has doomed you. Occaisional rebuilds of the desktop may help, restraint
as to the number of files per volume seems to help (older systems seem to
have unadvertised limits to the number of files they can catalog in the
finder DB, perhaps 1500).
> Just before Symantec ceased to support this product, I found out,
>they had announced a "Release 5" free of charge
As I recall, V8.0 and v8.5 were shrinkwrap releases.
v8r6 was the last release, it was not advertised, you had to do a song &
dance over the phone to a supervisor at S Customer Service to get it, any
prior version of S C++ made you eligible for it as an 'upgrade'. I dont
think it is available any longer, they claimed a small supply, if true it
is long gone by now, along with the group doing customer support for Mac
development tools.
V8r6 included TCL v2.0.9, Cafe LIght 1.5, and other goodies.
--
Dana S. Emery
dem...@ieaccess.net
You do not need to remove the .cpp files and the .rsrc ressource files.
Then rebuild and choose run with debugger in the project menue.
This helps in most cases.
If you decide to remove the whole Symantec C++ folder remember to remove
the whole project files either.They become corrupt if a .pef debuggable
binary crashes in the debugger.
Ah, and remove the pef file either. A corrupt pef file hinders the debugger
to invoke the debuggable binary. It simply becomes a programm which never
enters the event loop anymore (or processes events somehow) and therefore
is not to quit anymore with a quit apple event.
In article <76thog$noe$1...@sparky.wolfe.net>, "Robert Gulledge"
<rgul...@compu-teach.com> wrote:
>I'm stuck using Symantec's compiler for now and I can't figure out why the
>debugger crashes whenever I try and run any project using the debugger.
>
>It crashes on my old Quadra 660 sys 7.5 and my PowerMac 7200 system 8.1
>
>Both the 8.0x and the 7.0x versions crash.
>
>I tried booting with all extensions off and still no luck.
>
>I know that I had no problems using my ancient LC III System 7.0 way back
>when using Symantec 7.0
>
>- Robert
--
end of mail
This posting does not constitute agreement on my part to have my
email-address added to ANY mailing lists or to receive "one time" mailings
of a bulk or commercial nature.This is a automatized mail footer. Thank you
for taking note.
Freunliche Gruesse,
Robert Welz