🚀 go-pugleaf

I took your advise and tried it all -- it's been a week now and I'm ready to
give up
I tried w/ CW Pro 5, Pro 5.3, Pro 6.0 -- nothing
I do not think it has anything to do w/ caching or a memory leak in the
debugger -- I get the problem right away, first run, any line in the main;
i.e. freshly build, freshly run, even tried restarting OS before running,
etc.
I'd really like to get The Debugger (I assume you mean MWDebug) -- I only
have Pro 4, 5 and 6 -- who should I contact to get MWDebug from CW Pro 2 or
whatever version it came with last

FYI: the appl. xSYM file is about 3MB
apparently, when I step, the debugger does stop, but there is no context
info: the debug window says that the appl is executing, but the processes
window tells me that the (main) thread is stopped
what may cause the debugger to loose its context? -- please do not tell me
that the Data folders are corrupted, I've rebuild it today a thousand times
already (thrown Data folders away, yada,yada, yada)

any other things I could try? any settings that may cause this?
TIA,
--Ranko

"MWRon" <mwron@metrowerks.com> wrote in message
news:mwron-1801012059530001@c243286-a.bcreek1.mi.home.com...
> 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