🚀 go-pugleaf

In article <3a670a68$0$4491$73bec57d@news.be.uu.net>, "Ranko Orlic"
<ranko@scenicsoft.com> wrote:

>Hi guys,
>
>While trying to debug a large project that I've inherited, I've found my CW
>Pro 5.3 debugger to stop responding if I hit Step Into or Step Over? The
>only thing you can do is kill the appl. Anyone seen this before? Note that
>setting breakpoints works fine. You can hit Debug and jump from breakpoint
>to breakpoint.
>I tried rebuilding all, turning off MacsBug, turning off all extensions,
>replacing MetroNub w/ the one from Pro 6, thrown away Data folders, ...
>hell, I've even reinstalled MacOS 9.0.4 and CW, nothing helped.

Is there some reason you can't use CodeWarrior 6 for this project?

What this sounds like (and I know Dave is going to rack me over for saying
this), is your application is killing the debugger, but it also could be a
memory leak in the debugger if this is after a long session. 

>After 4 days, I'm ready to toss my Mac out the Windows (:o), so please,
>please, please, there must be a brave soul out there that is willing to save
>this poor Mac?

If this is a memory leak in CodeWarrior or in the debugger All I can think
of is running to a break point and keep moving it ahead each time and
doing fresh debugger settings. 

I wish I had better advice,  I don't recall this as a bug in 5.3 debugger.

Ron

-- 
CodeWarrior PersonalJava Edition v6  J2SE,  J2ME
services for CLDC/MIDP enabled wireless devices
http://www.metrowerks.com/java/

Metrowerks  "Software Starts Here"   MWRon@metrowerks.com