🚀 go-pugleaf

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

>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;

It could be something in your initialization and global code that is
causing this, can you put a break in that and then turn of the stop and
main and go through that?

did you try upping the partition for CodeWarrior,  (for your application).

>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

The Debugger is a low level debugger from Jasik, it is excellent but is 
rather expensive and hard to work with.  Still it works below the
Macintosh OS rather than on it like CodeWarrior does so it can't be
stepped on by your application at all.

You might try MacsBug it might tell you something.
 
>any other things I could try? any settings that may cause this?

You know upping the memory partition for your application and CodeWarrior
might help, but I'm sure you've done that.  There isn't a lot we can do
remote like this.

Oh can you break your program up into more testable components?

Send in a bug report but you'd need to send everything in.  We can sign
NDA's if you need them.

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