From: Jim Ingham <jingham@apple.com>
To: Nick Roberts <nick@nick.uklinux.net>
Cc: gdb@sources.redhat.com
Subject: Re: Apple version gdb-309
Date: Tue, 30 Mar 2004 17:50:00 -0000 [thread overview]
Message-ID: <1355A1BF-81DA-11D8-95CB-000A958F4C44@apple.com> (raw)
In-Reply-To: <16488.44975.558839.361364@nick.uklinux.net>
On Mar 29, 2004, at 3:22 PM, Nick Roberts wrote:
>
>>> More specifically will the future versions for Mac OS
>>> ( == powerpc-apple-darwin? ) have the changes for -stack-list-locals
>>> and
>>> -var-list-children that I committed to the FSF repository on
>>> 2004-01-20?
>>
>> Yes. Both these commands are different in our gdb from the version in
>> the FSF repository, but as I merge the differences, I will try to keep
>> the behavior you added working. It doesn't look too hard, though in
>> the case of stack-list-locals, your change uses argument values that
>> we
>> had already taken (I think Jason mentioned this at the time you were
>> adding it). So I have to get Xcode to change as well. Fortunately
>> for
>> now we keep the Xcode and gdb versions in sync, so this won't be a
>> problem...
>
> Jim,
>
> I did say to Jason (12 Dec 2003):
>
> Me> I don't see why both our changes can't be accommodated. This patch
> uses a
> Me> switch statement for each value of print_values. If for some
> reason Apple
> Me> need -stack-list-locals 2, I dont mind using another value.
>
> He didn't seem enthusiastic but perhaps I missed his point. All my
> changes to
> Emacs and GDB are still in CVS, so, as far as I'm concerned, you're
> welcome to
> change my values if this makes things easier for your merge.
I think Jason's point was that as long as we were just using numbers,
we were going to keep stepping on each other's toes, and it would be
better to use string enumerators. That would make code that users of
the mi would write easier as well. So there is no reason to go out of
our way fixing something that was not a very good solution in the first
place...
And it won't be hard to get the Xcode folks here to adjust to this, so
I'll just fix it here for now. But then we should cook up a set on
name strings to stand in the place of the {0,1,2} arguments that we
currently use.
Jim
--
Jim Ingham jingham@apple.com
Developer Tools
Apple Computer
next prev parent reply other threads:[~2004-03-29 23:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-30 7:05 Jim Ingham
2004-03-30 17:46 ` Nick Roberts
2004-03-30 17:50 ` Jim Ingham [this message]
2005-05-12 23:53 ` Nick Roberts
-- strict thread matches above, loose matches on Subject: below --
2004-03-29 23:35 Nick Roberts
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1355A1BF-81DA-11D8-95CB-000A958F4C44@apple.com \
--to=jingham@apple.com \
--cc=gdb@sources.redhat.com \
--cc=nick@nick.uklinux.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox