🚀 go-pugleaf

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