My experiences upgrading to CW Pro 7EA

Thread View: comp.sys.mac.programmer.codewarrior

4 messages

[T] Back to Threads [V] Tree View [G] Group Articles

4 total messages Started by Mark Taylor Wed, 13 Jun 2001 22:02

#1187

Author: Mark Taylor
Date: Wed, 13 Jun 2001 22:02

45 lines
2531 bytes

I am working on a Carbonized app on OS X 10.0.3 with the WWDC Dev Tools
installed on a PB G4.  I have just updated to CW Pro 7EA after getting
frustrated with CW Pro 6.2.

Here are some notes regarding my experience.


First, the good news:

1. The editor works much faster now (it's now usable).

2. I no longer have to wiggle the mouse to get the debugger to appear.

3. Debug > Kill works without having to quit MetroNubX and restart the IDE.

4. Debug > Restart works now.

5. For Pro 6.2, I had made the suggested links as follows:

      cd /System/Library/Frameworks
      ln -s Carbon.framework CarbonCore.framework
      ln -s Carbon Carbon.framework/Versions/A/CarbonCore

   which eliminated the need to manually launch DebugNub Controller and
hit "Start".  This workaround is no longer needed for 7EA.


Now, the bad news, in order of annoyance factor:

1. The debugger still takes about 30 seconds to launch.  This is due to
gdb, according to ProcessViewer.

2. Each step in the debugger takes approximately two seconds.

3. The "Step over == Step into" bug is still there.

4. Debugging now no longer works under CW Pro 6.2.  The app to be tested
gets launched but the stack window never appears.  Maybe the gdb update
caused this?  So there's no turning back.
   

I'm looking forward to the 7EA update Ron mentioned.  Ron, what kind of
performance improvement can we expect?

- Mark

Re: My experiences upgrading to CW Pro 7EA

#1188

Author: MWRon
Date: Thu, 14 Jun 2001 02:57

46 lines
2240 bytes

In article <taylor-1306011702030001@192.168.1.102>,
 taylor@alumniDOTprinceton.edu (Mark Taylor) wrote:

Didn't you write this note a week ago?

>Now, the bad news, in order of annoyance factor:
>
>1. The debugger still takes about 30 seconds to launch.  This is due to
>gdb, according to ProcessViewer.

I was told that we had received a new gdb from Apple and were testing it.

>2. Each step in the debugger takes approximately two seconds.

Combination of gdb and MetroNubPlugin  number variables, etc.

> the "Step over == Step into" bug is still there.

Supposedly fixed in this newest GDB  

>4. Debugging now no longer works under CW Pro 6.2.  The app to be tested
>gets launched but the stack window never appears.  Maybe the gdb update
>caused this?  So there's no turning back.

Gog no idea. 

>I'm looking forward to the 7EA update Ron mentioned.  Ron, what kind of
>performance improvement can we expect?

It is going to be a good performance improvement but it is not going to 
be like debugging on Mac OS 9  applications.    And as always your 
milage may vary.

Can't give you a date or any specifics it isn't even into beta testing 
yet.

Ron

-- 
Metrowerks announces host of new Wireless Java tools at JavaOne

Java Support Newsgroups: codewarrior.java, codewarrior.java.embedded

Metrowerks - Ron Liechty - MWRon@metrowerks.com

Re: My experiences upgrading to CW Pro 7EA

#1189

Author: Mark Taylor
Date: Thu, 14 Jun 2001 15:59

20 lines
1785 bytes

In article <mwron-F3AD6F.22570013062001@enews.newsguy.com>, MWRon
<mwron@metrowerks.com> wrote:

> Didn't you write this note a week ago?
> 

Couldn't have been me, since I just upgraded to 7EA yesterday, but I know
I'm not the first to comment on the state of the debugger here.

> It is going to be a good performance improvement but it is not going to 
> be like debugging on Mac OS 9  applications.    And as always your 
> milage may vary.
> 

I wonder if it will EVER be like debugging on OS 9.  Do you sense a
commitment on Apple's part to help Metrowerks make this happen?  Surely
there are still people at Apple using CodeWarrior these days.  They've
gotta be hurting too.

- Mark

Re: My experiences upgrading to CW Pro 7EA

#1190

Author: MWRon
Date: Thu, 14 Jun 2001 22:40

30 lines
2115 bytes

In article <taylor-1406011059210001@192.168.1.102>,
 taylor@alumniDOTprinceton.edu (Mark Taylor) wrote:

>I wonder if it will EVER be like debugging on OS 9.  Do you sense a
>commitment on Apple's part to help Metrowerks make this happen?  Surely
>there are still people at Apple using CodeWarrior these days.  They've
>gotta be hurting too.

Yes there is a lot of cooperation going on.

What we need to make better understood is that this is a new operating 
system.  FreeBSD Mach-O is not the Linux kernel, and OS X is not a 
remake of Mac OS.   It took Microsoft at least 4 years after NT was 
released to get NT working as well as OS X does now.     I think there 
is a lot of Kudo's to Apple's engineers on and to Metrowerks engineers 
for coming so far so fast.  But this is a new operating system.  

Right now it is going to take some more work to get debugging to be 
effortless but we are working on it.  I think CW 8 before it is 
something to be proud of but if we can make it sooner we will.

Ron

-- 
Metrowerks announces host of new Wireless Java tools at JavaOne

Java Support Newsgroups: codewarrior.java, codewarrior.java.embedded

Metrowerks - Ron Liechty - MWRon@metrowerks.com

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads