Re: Remote debugging in Xcode 2.3 on 10.2.8
Re: Remote debugging in Xcode 2.3 on 10.2.8
- Subject: Re: Remote debugging in Xcode 2.3 on 10.2.8
- From: Mark Stultz <email@hidden>
- Date: Fri, 02 Jun 2006 18:34:07 -0500
Backward compatibility has become extremely annoying. I should have posted
Chris's email instead of saying "refer to the archives". It's Friday, it's
6:30 and I'm still in the office with the sun burning into this room through
the blinds. I feel like I spend a lot of my time with insignificant issues
such as these, than actual coding.
I wish we had some hard numbers on usage of the various Mac OS X versions.
I'm so ready to drop 10.2.8 support. However, we do casual games--a market
that I'm sure doesn't upgrade so readily. You have to admire Apple's
decisions to require the latest and greatest with many of their
applications.
Mark
On 6/2/06 6:23 PM, "Jason Molenda" <email@hidden> wrote:
> That won't help Mark - he alluded to Chris' workaround in his e-mail.
> Chris' workaround was to fix a problem with MacOS X 10.4 (Xcode 2.3) -
>> MacOS X 10.3 remote debugging. Mark is trying to do MacOS X 10.4
> (Xcode 2.3) -> MacOS X 10.2 remote debugging and it's hitting a
> different issue.
>
> It may be possible to do a similar bit of trickery to get this working
> but that's such an old set of tools on MacOS X 10.2 that someone would
> have to do some real testing before they could present anything as
> being "usable".
>
> J
>
>
> On Jun 2, 2006, at 4:18 PM, Alexander von Below wrote:
>
>> Here is the solution Chris posted on this list, and I am resending
>> it without giving the usual "search the archives" talk because I
>> consider it a very important topic.
>>
>>
>>
>>> Xcode 2.3 is passing a new argument to the gdb machine interface
>>> for setting breakpoints that 10.3's gdb doesn't understand. We can
>>> change the data stream to gdb on your 10.3 machine by changing /usr/
>>> bin/gdb on the 10.3 machine. I haven't tested this on a 10.3
>>> install (Note from Alex: I have successfully done so):
>>>
>>> 1. On your 10.3 machine backup /usr/bin/gdb
>>>
>>> sudo cp /usr/bin/gdb /usr/bin/gdb.orig
>>>
>>> 2. On your 10.3 machine edit /usr/bin/gdb with your favorite
>>> command line editor
>>>
>>> sudo pico /usr/bin/gdb
>>>
>>> Then change the last line
>>>
>>> exec "$gdb" "$@"
>>>
>>> to
>>>
>>> exec perl -e 'while($len = sysread(STDIN, $buf, 1024)){$buf =~ s /-
>>> break-insert -l -1/-break-insert/g; syswrite(STDOUT, $buf, $len);}'
>>> | "$gdb" "$@"
>>>
>>> (Note: Originally Chris had posted a sed line, which did not work)
>>>
>>> I'll filed a Radar on this.
>>>
>>> Cheers,
>>> ChrisF
>>
>> On 03.06.2006, at 01:09, Mark Stultz wrote:
>>
>>> Hello all,
>>>
>>> I've been experiencing some insane errors on 10.2.8 of a project
>>> I'm working
>>> on. For some reason the call stack seems to be calling functions
>>> that I am
>>> not expecting. I figured a little remote debugging would be a
>>> tremendous
>>> help, but I have not been able to successfully do this on 10.2.8.
>>> I can get
>>> the debugging working, and the 10.2.8 remote machine will launch
>>> the game. I
>>> can pause and quit. However, I cannot set breakpoints. I utilized
>>> the
>>> scheme found on the Apple lists entitled "debug universal binary on
>>> 10.3?".
>>> It talks about getting around the:
>>>
>>> mi_cmd_break_insert: Unknown option ''l""
>>>
>>> However, I am not getting the following error while setting
>>> breakpoints:
>>>
>>> mi_cmd_break_insert: Unknown option ``s''
>>> Unable to set breakpoint . Make sure to build the file with
>>> debugging
>>> symbols.
>>>
>>> The project definitely has debugging symbols. Any help is
>>> appreciated.
>>>
>>> Mark
>
_______________________________________________
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