🚀 go-pugleaf

On Thu, 18 Jan 2001 7:24:18 -0800, Ranko Orlic wrote
(in message <3a670a68$0$4491$73bec57d@news.be.uu.net>):

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

I'll probably get racked for this, but you could try MWDebug, if this works 
then most likely you've hit one of the "non reprodcucable" debugger problems. 
It shouldn't take more than 15 mins to find out and if you've already 
invested:

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

I know EXACTLY how you feel, I remember it being 4 AM, by eyes were bluring, 
so that when the "�����Invalid Register�����" text appeared, I didn't quite 
realize the full extent of my woes, it took an extra 3 or 4 minutes for it to 
hit me that I'd just lost 5 hours of work!!

---Dave

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

In article <01HW.B68C825600032B0309969B70@news.earthlink.net>, David
Burgun <NOdburgunSPAM@earthlink.net> wrote:

>I'll probably get racked for this, but you could try MWDebug, if this works 
>then most likely you've hit one of the "non reprodcucable" debugger problems. 
>It shouldn't take more than 15 mins to find out and if you've already 
>invested:

No I won't rack you for this one,  if this is an option it might at least
show a problem somewhere else or not crash at all even if it is a bug in
the program. 

There always is  The Debugger too which certainly will not get messed with
by an errant application.

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

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

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

On 1/18/01 8:24 AM, 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.
> 
> 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?
> 
> cheers,
> --Ranko


Strangely enough I think I have seen this before. I had an application
started in carbon  and then the specs changed and it turned into a straight
Classic app. So while decarbonating it, I typed in the initialization mantra
and forgot one. If memory serves, it was TEInit(). The debugger got to a
weird place where it would run to breakpoints but not step. I resorted to
MacsBug till I found the problem.



-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----==  Over 80,000 Newsgroups - 16 Different Servers! =-----

I found it!
you are NOT going to believe this :o) -- it turns out to be preference
setting ?!

Under Edit | Preferences... | Debugger | MetroNub Settings | Window Settings
there is the option to "Keep program in background while stepping" -- by
default, when you install MWCW, it is on/checked.
If on, I can set and hit breakpoints but I cannot step into or step over my
source code.
If I turn it off, all goes well ???

Ron, any ideas why this happens?

--Ranko

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

>you are NOT going to believe this :o) -- it turns out to be preference
>setting ?!

Yikes !!  I've not hear this before and it does not sound good.

>Under Edit | Preferences... | Debugger | MetroNub Settings | Window Settings
>there is the option to "Keep program in background while stepping" -- by
>default, when you install MWCW, it is on/checked.
>If on, I can set and hit breakpoints but I cannot step into or step over my
>source code.
>If I turn it off, all goes well ???
>
>Ron, any ideas why this happens?

Please report this to  <cw_bug@metrowerks.com>  The bug report and other
forms are in the CodeWarrior Release Notes : email Report Forms folder. 
Be sure to include all details and if possible,  a simple example project
with source codes and headers.


Ron

-- 
               "GEEKWARE IS BACK"

http://www.metrowerksstore.com/geekware.html

Metrowerks  "Software Starts Here"   MWRon@metrowerks.com

On Wed, 24 Jan 2001 6:41:23 -0800, MWRon wrote
(in message <mwron-2401010941230001@c243286-a.bcreek1.mi.home.com>):

> In article <3a6eaf52$0$4491$73bec57d@news.be.uu.net>, "Ranko Orlic"
> <ranko@scenicsoft.com> wrote:
> 
>> you are NOT going to believe this :o) -- it turns out to be preference
>> setting ?!
> 
> Yikes !!  I've not hear this before and it does not sound good.
> 
>> Under Edit | Preferences... | Debugger | MetroNub Settings | Window 
>> Settings
>> there is the option to "Keep program in background while stepping" -- by
>> default, when you install MWCW, it is on/checked.
>> If on, I can set and hit breakpoints but I cannot step into or step over my
>> source code.
>> If I turn it off, all goes well ???
>> 
>> Ron, any ideas why this happens?
> 
> Please report this to  <cw_bug@metrowerks.com>  The bug report and other
> forms are in the CodeWarrior Release Notes : email Report Forms folder. 
> Be sure to include all details and if possible,  a simple example project
> with source codes and headers.
> 

Actually I'm not sure this is a bug. If you go to the MacOS/Finder 
Application menu and re-select your App, can you now continue?

---Dave

nope, it's grayed-out

--Ranko

"David Burgun" <NOdburgunSPAM@earthlink.net> wrote in message
news:01HW.B6947A9F000613820913BC80@news.earthlink.net...
[snip]
> Actually I'm not sure this is a bug. If you go to the MacOS/Finder
> Application menu and re-select your App, can you now continue?
>
> ---Dave
>