Re: GDB can't debug PPC on Intel
Re: GDB can't debug PPC on Intel
- Subject: Re: GDB can't debug PPC on Intel
- From: Brock Brandenberg <email@hidden>
- Date: Sat, 27 May 2006 18:09:39 -0500
Hi Eric.
On May 27, 2006, at 4:59 PM, Eric Albert wrote:
On May 27, 2006, at 2:52 PM, Brock Brandenberg wrote:
I don't know where to start with this issue. In the progress of
watching GCD crash when trying to start debugging a PPC app on an
Intel MacBook Pro, it has managed to leave processes running that
don't show CPU usage in Activity Monitor, yet both CPU cores are
clearly going at about 60% each with the fans running on the
machine. The disk activity is high, and doing fs_usage reveals
some "nmbd" process writing to disk about 60 times a second.
'man nmbd' will show you that nmbd is part of Samba, which is the
Windows file sharing environment. Turn off Windows file sharing in
the Sharing pane of System Preferences if you want it to go away.
It has nothing to do with the developer tools.
Noted, thanks. However, the crash of GDB trying to run from within
XCode is definitely causing some process to crank up CPU usage to a
seriously high level and never stop. It's 100% repeatable if when I
try running the debugger from XCode two or three times after a fresh
restart (waiting long enough to insure that the usage isn't the
result of some other process). The only way to end the CPU usage is a
restart. All I can see from the list of processes in Activity Monitor
is about 5% total CPU usage, but disk activity shows data written I/O
of about 240KB/sec and the CPU graphs and bars show at least 60% per
core. The nmbd process and mds process appear to be the only ones
using the disk, so maybe GDB is leaving some cache files behind that
SpotLight continues to try and index, but never succeeds? I'm
clueless at this point and tired of restarting. At least I can now
stop trying to debug...
Back to the inability to debug PPC on Intel. I have a Carbon app
that I'm trying to target to the 10.2.8 SDK, a OS 10.2 deployment
target, the PPC architecture and build with GCC 3.3. When running
the debugger, GDB exits with error 1 after the message
"Architecture of file not recognized."
Debugging applications running in Rosetta requires some additional
setup that you don't have to do for native applications. See
<http://developer.apple.com/documentation/MacOSX/Conceptual/
universal_binary/universal_binary_exec_a/chapter_7_section_8.html#//
apple_ref/doc/uid/TP40002217-CH210-235927> for details.
Hope this helps,
Yes, it helps a lot. It ends my trial-and-error and archive
searching, and increases my distaste for this Intel chip
transition :/ While the Intel machines are faster, the transition and
maintenance for old PPC code is proving to be a pain in the ass. I
guess the only option is to keep a second machine around for
debugging and maintaining the PPC code.
Thanks for the quick response.
Brock
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden