On Mar 25, 2010, at 07:55, Jon Pugh wrote:
At 12:02 AM -0700 3/25/10, Brian Willoughby wrote:
Switch to an Intel Mac, or revert to an older version of Xcode.
This was unfortunately broken in the last release of Xcode for
Leopard, but only on PPC Macs, and I wouldn't hold your breath
waitin
At 12:02 AM -0700 3/25/10, Brian Willoughby wrote:
>>Switch to an Intel Mac, or revert to an older version of Xcode. This was
>>unfortunately broken in the last release of Xcode for Leopard, but only on
>>PPC Macs, and I wouldn't hold your breath waiting for a fix.
>
>
>Thanks. That's the kind o
On Mar 24, 2010, at 19:17, Nick Zitzmann wrote:
On Mar 24, 2010, at 7:44 PM, Brian Willoughby wrote:
Another potentially important detail is that I am running Leopard
10.5.8 on a 1.67 GHz PowerPC G4 PowerBook with 2 GB RAM.
Any ideas how to fix this? Do I need an even older release of
Xco
I sometimes have that problem on Snow Leopard too. Relatively rare, thank
goodness, but certainly an issue sometimes.
Gideon
On 25/03/2010, at 12:17 PM, Nick Zitzmann wrote:
>
> On Mar 24, 2010, at 7:44 PM, Brian Willoughby wrote:
>
>> Another potentially important detail is that I am running
On Mar 24, 2010, at 7:44 PM, Brian Willoughby wrote:
> Another potentially important detail is that I am running Leopard 10.5.8 on a
> 1.67 GHz PowerPC G4 PowerBook with 2 GB RAM.
>
> Any ideas how to fix this? Do I need an even older release of Xcode 3.x to
> get proper debugger operations o
Hi folks,
I am having trouble with Xcode where the "Step Into" button in the
debugger is acting just like "Step Over."
One project is newly created under 3.1.4, as a Foundation Tool, and I
find that I cannot "Step Into" any of my Objective C methods. The
only workaround is to place break
