From: Jason Molenda <jmolenda@apple.com>
To: Nick Roberts <nick@nick.uklinux.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFC (gdb/mi): -stack-list-locals
Date: Fri, 12 Dec 2003 23:01:00 -0000 [thread overview]
Message-ID: <F5599E07-2CF6-11D8-89D0-000393D457E2@apple.com> (raw)
In-Reply-To: <16346.10340.488095.107663@nick.uklinux.net>
On Dec 12, 2003, at 12:43 PM, Nick Roberts wrote:
> Jason Molenda writes:
>
>> ...Right now we have a
>> non-standard meaning for -stack-list-locals 2, and the FSF gdb will
>> have a different meaning for 2 with this patch going in. No
>> complaints
>> or anything, but it's unpleasant.
>
> I don't see why both our changes can't be accommodated.
Well, if we're both implementing a different meaning for "2" that's a
pretty tough thing to accommodate. :-)
I didn't mean my statement as a criticism of this change or the work
you're doing -- this is the sort of thing we inevitably have come up
when we have lots of changes vs. the mainline. We made our bed, etc.
> This patch uses a
> switch statement for each value of print_values. If for some reason
> Apple need
> -stack-list-locals 2, I dont mind using another value.
"3" would be very nice. :) But really, I think Andrew's suggestion is
a better approach. Instead of numeric values which represent an
arbitrary collection of return values ("2" is "the things Apple's UI
would like to get", "3" is "a smaller set of things that don't involve
so much communication with the inferior"), text strings are a little
less likely to conflict.
> Everybody seems to
> want Apple's changes, including their management. Rather than being
> unpleasant, perhaps this is an opportunity to make the case to that
> management
> for resources to contribute back to the FSF.
Yeah, it's the usual problem. Lots to do, not so much time in which to
do it, sigh.
J
next prev parent reply other threads:[~2003-12-12 23:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-23 0:16 Nick Roberts
2003-11-26 0:48 ` Andrew Cagney
2003-12-02 3:14 ` RFC (gdb/mi): -stack-list-locals + PATCH Nick Roberts
2003-12-09 2:42 ` RFC (gdb/mi): -stack-list-locals + REVISED PATCH Nick Roberts
2003-12-10 17:56 ` Andrew Cagney
2003-12-10 22:26 ` Jason Molenda
2003-12-12 20:51 ` RFC (gdb/mi): -stack-list-locals Nick Roberts
2003-12-12 21:09 ` David Carlton
2003-12-17 2:29 ` [PATCH: gdb/mi + doco] -stack-list-locals and -var-list-children Nick Roberts
2003-12-17 2:32 ` David Carlton
2003-12-17 18:51 ` [PATCH: gdb/mi] -stack-list-locals Nick Roberts
2003-12-17 21:21 ` David Carlton
2003-12-17 18:05 ` [PATCH: gdb/mi + doco] -stack-list-locals and -var-list-children Eli Zaretskii
2004-01-05 21:43 ` Andrew Cagney
2004-01-06 0:14 ` [PATCH: gdb/mi] -stack-list-locals testcase Nick Roberts
2004-01-06 1:07 ` Andrew Cagney
2004-01-07 16:31 ` Andrew Cagney
2004-01-07 17:34 ` Mark Kettenis
2004-01-07 17:40 ` Daniel Jacobowitz
2003-12-12 23:01 ` Jason Molenda [this message]
[not found] <1069611654.20143.ezmlm@sources.redhat.com>
2003-12-01 19:27 ` RFC (gdb/mi): -stack-list-locals Jim Ingham
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=F5599E07-2CF6-11D8-89D0-000393D457E2@apple.com \
--to=jmolenda@apple.com \
--cc=gdb-patches@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