ham@polya.Berkeley.EDU (Peter R. Ham) (08/18/88)
My group is dying to use the LCS 3.0 debugger. One problem is that our project is not mulitfinder compatible. Another problem is that one of us has tried it out and the version we have (without patches) corrupts his probjects? Has anyone out there had similar problems? Do you have the latest patches? Is it really true that your application must be multi-findeer compatible to run unde
jwhitnell@cup.portal.com (08/19/88)
Peter R. Ham got truncated saying... | My group is dying to use the LCS 3.0 debugger. One problem is that |our project is not mulitfinder compatible. Another problem is that one of |us has tried it out and the version we have (without patches) corrupts |his probjects? Has anyone out there had similar problems? Do you have |the latest patches? Is it really true that your application must be |multi-findeer compatible to run unde You need to remember to put <CR> in your text, otherwise your message gets truncated. Since LSD runs under MutliFinder, your project has to also work with MutliFinder. The most likly cause of project corruption is wild pointers. Since there is no memory protection and LSC doesn't do any checking of its own heap space, any writes to a pointer that points to the wrong place can and will corrupt your project. LSC really needs to checksum its own heap for protection. -- Jerry Whitnell jwhitnell@cup.portal.com ...!sun!portal!jwhitnell