Pro6 + OSX Debugging Solution

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

3 messages

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

3 total messages Started by Bill Evans Wed, 04 Oct 2000 04:28

#1393

Author: Bill Evans
Date: Wed, 04 Oct 2000 04:28

59 lines
3464 bytes

I finally got CW Debugging working properly under OS X Public Beta.

My setup is:
````````````
- PowerBook G3 292 MHz with 192 Megs of RAM
- OS 9.0.4 installed on first 3.8 Meg partition
- OS X Public Beta + Developer Tools installed on second 3.8 Meg
partition
- ethernet network with a 100 BT switch plus a Linksys cable router as
gateway to the internet

Initial installation that caused the problems:
``````````````````````````````````````````````
- had installed Metrowerks Codewarrior on first partition
- my projects were in a folder on first partition
- OS X on second partition
- don't know if it's relevant, but my 1st partition name is "Precious
Little" and the second was the default "Mac OS X"

What didn't work in above scenario:
```````````````````````````````````
- Codewarrior would try to fire up debugging and came back with network
connection errors
- firing up DebugNub myself and changing the port from 6969 to 6968
caused a crash error dialog (bus error)
- running DebuNub from the command line (DebugNub -p 6968) gave me all
sorts of errors saying that there were NULL pointers, etc... in gdb

Last installation that finally works:
`````````````````````````````````````
- wiped and reinstalled OSX
- installed Dev Tools
- removed Codewarrior from 1st partition
- installed Codewarrior into /Developer on the second partition WHILE
RUNNING OS X
- I have enabled Appletalk, but don't think that makes a difference

Initial problems with this last installation:
`````````````````````````````````````````````
- as noted by the illustrious meeroh, MetroNubX doesn't seem to have
the execute flag set... so, in my case I did the following from
Terminal:

chmod x+a /Developer/Metrowerks CodeWarrior 6.0/Metrowerks
CodeWarrior/CodeWarrior
Plugins/Debuggers/MetroNubX.app/Contents/MacOS/MetroNubX

(that is all one line)

Before I did that, debugging worked fine if I ran DebugNubController on
port 6968 before I tried to debug with CodeWarrior. After I changed the
permissions, CodeWarrior fires up gdb itself on the correct port.

I hope this helps someone and I sincerely hope someone at Metrowerks
reads this and addresses the issue. I am really glad now that I have
dabbled with Linux for the past 2 years and am very comfortable poking
about with the command line.

-Bill (not)

Re: Pro6 + OSX Debugging Solution

#1394

Author: meeroh
Date: Wed, 04 Oct 2000 04:43

11 lines
1364 bytes

In article <031020002128216102%bill@greeneggsandspam.com>, Bill Evans 
<bill@greeneggsandspam.com> wrote:

>I finally got CW Debugging working properly under OS X Public Beta.

Great! Now, whenever someone asks me how to get it to work, I'll point 
them at you instead of telling them to read the release notes :-)

meeroh
-- 
To get random signatures put text files into a folder called �Random Signatures� into your Preferences folder.

Re: Pro6 + OSX Debugging Solution

#1395

Author: Bill Evans
Date: Thu, 05 Oct 2000 00:00

12 lines
1401 bytes

Just to follow up my post on getting the debugger working...

Make sure your project is in your OS X home directory. This seems to
work the best. If you are running a project from another volume,
MetroNubX gets confused. You can still manually run DebuggerNub on port
6968 and press OPTION while clicking the Run/Debug button in the
project manager. This forces CodeWarrior to look for an already running
DebugNub process.

Yes, that last bit I gleaned from the release notes :-)

-Bill (not)

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