Article View: comp.sys.mac.programmer.codewarrior
Article #1393Pro6 + OSX Debugging Solution
From: Bill Evans
Date: Wed, 04 Oct 2000 04:28
Date: Wed, 04 Oct 2000 04:28
59 lines
3464 bytes
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)
Technical Details
Message-ID:
<031020002128216102%bill@greeneggsandspam.com>Path:
arc1-ca.pugleaf.net!supernews.google.com!sn-xit-02!sn-xit-03!supernews.com!newsfeed.direct.ca!look.ca!newshub2.rdc1.sfba.home.com!news.home.com!news1.rdc1.bc.home.com.POSTED!not-for-mailShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 10bcce,1d1dff6f5d1544ba,start X-Google-Attributes: gid10bcce,public X-Google-Thread: f635e,1d1dff6f5d1544ba,start X-Google-Attributes: gidf635e,public X-Google-ArrivalTime: 2000-10-03 21:28:44 PST Path: arc1-ca.pugleaf.net!supernews.google.com!sn-xit-02!sn-xit-03!supernews.com!newsfeed.direct.ca!look.ca!newshub2.rdc1.sfba.home.com!news.home.com!news1.rdc1.bc.home.com.POSTED!not-for-mail Subject: Pro6 + OSX Debugging Solution From: Bill Evans <bill@greeneggsandspam.com> Newsgroups: comp.sys.mac.programmer.codewarrior,codewarrior.mac Message-ID: <031020002128216102%bill@greeneggsandspam.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 8bit Mail-Copies-To: nobody User-Agent: YA-NewsWatcher/5.0.1 Lines: 59 Date: Wed, 04 Oct 2000 04:28:43 GMT NNTP-Posting-Host: 24.65.24.63 X-Complaints-To: abuse@home.net X-Trace: news1.rdc1.bc.home.com 970633723 24.65.24.63 (Tue, 03 Oct 2000 21:28:43 PDT) NNTP-Posting-Date: Tue, 03 Oct 2000 21:28:43 PDT Organization: Excite@Home - The Leader in Broadband