Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
General
GeneralPortable MacsHardwareNetworking
Applications
Mac ApplicationsEudoraFirefox / MozillaInternet ExplorerOutlook ExpressMS OfficeEntourageExcelPowerPointWordVirtual PCMedia PlayerOther MS Products
Programming
Mac ProgrammingCodeWarriorPerl
Country Specific
Australian Mac GroupUK Mac Group

Mac Forum / Programming / CodeWarrior / April 2008



Tip: Looking for answers? Try searching our database.

CodeWarrior on Leopard (PPC) and debugging

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Robert Welz - 26 Mar 2008 09:32 GMT
Hello!

Did someone manage to use CodeWarrior on Leopard (PPC) and get the C++
debugger to work?

I have instelled CW on Leopard and it compiles fine but when I click
"debug" I can see in the process viewer app that "gdb-for-metrowerks"
launches but no debugger window opens.

Thanks for help!

Robert
Newsguy - 12 Apr 2008 16:57 GMT
Hi Robert,

I'm having the same problem.  Did you have any luck finding a solution?

I just installed CodeWarrior 10 on a new Mac laptop running OS X 10.5.2.
I've also installed XCode 3.  Upon starting CodeWarrior, I get two error
messages.  The first is "Apple Developer Tools Not Detected".  The 2nd is
"Interface Builder Connection Not Found".  But I've installed XCode into the
standard location.  Do you have an idea how to fix this?  Do I need to
install an earlier version of XCode?  If so, what is the latest version that
will work?

Also, is the comp.sys.mac.programmer.codewarrior newsgroup still active?
Are there other newsgroups that are still active?

-- Brian

> Hello!
>
[quoted text clipped - 8 lines]
>
> Robert
Jonathan Hoyle - 15 Apr 2008 14:20 GMT
> Hi Robert,
>
[quoted text clipped - 25 lines]
>
> > Robert

Have you tried to install Xcode 2.5?  Both Xcodes 2.5 and 3 can
coexist on the same Leopard system, but CodeWarrior is incompatible
with Xcode 3, and it at least has a decent shot of working with Xcode
2.x.
Ideas Live - 16 Apr 2008 12:33 GMT
I got CodeWarrior to find Xcode using both Xcode 2.5 and 3 by checking the
optional 10.3.9 comptability choice in the installer.  But when running the
debugger, it hangs - just sits there initializing and never completes.  I'm
running 10.5.2 on an Intel PowerBook, and I imagine this is either a Leopard
or an Intel mac issue.  Any ideas?

Thanks,

Brian

On Apr 12, 11:57 am, "Newsguy" <br...@ideaslive.com> wrote:
> Hi Robert,
>
[quoted text clipped - 31 lines]
>
> > Robert

Have you tried to install Xcode 2.5?  Both Xcodes 2.5 and 3 can
coexist on the same Leopard system, but CodeWarrior is incompatible
with Xcode 3, and it at least has a decent shot of working with Xcode
2.x.
nospam - 18 Apr 2008 04:08 GMT
> I got CodeWarrior to find Xcode using both Xcode 2.5 and 3 by checking the
> optional 10.3.9 comptability choice in the installer.  But when running the
> debugger, it hangs - just sits there initializing and never completes.  I'm
> running 10.5.2 on an Intel PowerBook, and I imagine this is either a Leopard
> or an Intel mac issue.  Any ideas?

it's an intel issue.
Jonathan Hoyle - 18 Apr 2008 21:31 GMT
> I got CodeWarrior to find Xcode using both Xcode 2.5 and 3 by checking the
> optional 10.3.9 comptability choice in the installer.  But when running the
[quoted text clipped - 5 lines]
>
> Brian

You cannot debug into a PowerPC application on an Intel Mac.  This is
not a CodeWarrior limitation, but a Mac one: the same limitation
exists when trying to debug into a PowerPC application built with
Xcode.  The reverse is true as well: you cannot debug into an Intel
application on your PowerPC-based Mac.

This is obviously less of a problem for those building universal
applications in Xcode, as you can debug into the native binary.

The CodeWarrior compiler/linker/IDE portion will run fine under
Rosetta emulation on your Intel-based Macintosh, but no debugging is
available.

Jonathan Hoyle
MacCompanion
http://www.jonhoyle.com
Ben Artin - 20 Apr 2008 15:45 GMT
> You cannot debug into a PowerPC application on an Intel Mac.  

This is not the case. See
<http://developer.apple.com/documentation/MacOSX/Conceptual/universal_binary/univ
ersal_binary_exec_a/chapter_950_section_8.html>. However, you can only do it
directly in gdb.

Ben

Signature

If this message helped you, consider buying an item
from my wish list: <http://artins.org/ben/wishlist>

Jonathan Hoyle - 21 Apr 2008 13:08 GMT
> In article <0f76ab6e-5708-4dae-a559-a02e7121b...@b1g2000hsg.googlegroups.com>,
>
[quoted text clipped - 6 lines]
>
> Ben

Yes, that is a good tip.  However, I was speaking of source-level
debugging within the development environment itself.  This procedure
does not do that, as it clearly states at the bottom:

"Debugging Rosetta applications from within either CodeWarrior or
Xcode is not supported."

However, the section you are describing is certainly a great way of
testing your PowerPC application's compatibility with Rosetta.

Jonathan Hoyle
MacCompanion
http://www.jonhoyle.com
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.