From: Stan Shebs <stan@codesourcery.com>
To: Hui Zhu <teawater@gmail.com>
Cc: tromey@redhat.com, Joel Brobecker <brobecker@adacore.com>,
Michael Snyder <msnyder@vmware.com>,
gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [RFC] Let "gcore" command accept a suffix argument
Date: Wed, 16 Dec 2009 15:49:00 -0000 [thread overview]
Message-ID: <4B29018C.6060307@codesourcery.com> (raw)
In-Reply-To: <daef60380912151957t312f3497l1e4022ce3dd8cbc4@mail.gmail.com>
Hui Zhu wrote:
> On Wed, Dec 16, 2009 at 03:20, Tom Tromey <tromey@redhat.com> wrote:
>
>>>>>>> ">" == Hui Zhu <teawater@gmail.com> writes:
>>>>>>>
>>>> Agree with you. Add " with variable make it oddness.
>>>> What about change it to others, like:
>>>> eval echo {++$a}
>>>>
>>>> Or add " to simple string, like:
>>>> eval echo ++$a".core"
>>>> Or
>>>> eval echo ++$a'.core'
>>>>
>> What do you think of the idea of making it printf-like?
>>
>
> It's not bad. But need a lot of extend work that the old patch don't have.
> And this command doesn't need convert a value from 1 type to another.
> So I want use the "" way.
>
BTW, Pedro nudges me out of my stupor and reminds me that the
soon-to-be-posted tracepoint action to evaluate without collecting is
also called "eval" (it was originally proposed as "do" but that
ambiguates with "down", which seemed like a bad idea).
The two versions are not necessarily mutually exclusive - the
downloading at the start of a trace run gives us a chance to filter out
eval's that don't make sense for the target agent - but if we go too
afield on syntax (the tracepoint version is simply a comma-separated
list of GDB expressions), then that's going to be more of a problem to
reconcile.
Stan
next prev parent reply other threads:[~2009-12-16 15:49 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4B11DA3C.3000203@vmware.com>
[not found] ` <daef60380911300437o4c616eb2v5ad7bfe99bd3c5e9@mail.gmail.com>
[not found] ` <20091130162246.GE4034@adacore.com>
[not found] ` <4B141157.3070709@vmware.com>
[not found] ` <20091130185341.GI4034@adacore.com>
[not found] ` <4B141469.5030402@vmware.com>
[not found] ` <20091130190619.GJ4034@adacore.com>
[not found] ` <4B1428F0.7090608@vmware.com>
[not found] ` <daef60380912091827u6ff7127bp1d03998a40932914@mail.gmail.com>
2009-12-10 2:32 ` Hui Zhu
2009-12-10 17:08 ` Tom Tromey
2009-12-11 10:06 ` Joel Brobecker
2009-12-11 18:25 ` Tom Tromey
2009-12-12 8:33 ` Hui Zhu
2009-12-13 4:05 ` Hui Zhu
2009-12-14 17:09 ` Tom Tromey
2009-12-15 1:57 ` Hui Zhu
2009-12-15 19:21 ` Tom Tromey
2009-12-16 3:58 ` Hui Zhu
2009-12-16 15:49 ` Stan Shebs [this message]
2009-12-17 2:45 ` Hui Zhu
2009-12-17 4:26 ` Joel Brobecker
2009-12-17 4:29 ` Michael Snyder
2009-12-17 9:32 ` Andreas Schwab
2009-12-21 20:15 ` Tom Tromey
2009-12-31 0:18 ` Stan Shebs
2010-01-04 14:42 ` Hui Zhu
2010-01-06 6:57 ` Hui Zhu
2010-01-06 7:58 ` Joel Brobecker
2010-01-09 9:55 ` Hui Zhu
2010-01-09 10:56 ` Joel Brobecker
2010-01-09 15:18 ` Hui Zhu
2010-01-10 5:43 ` Joel Brobecker
2010-01-10 13:30 ` Hui Zhu
2010-01-10 14:00 ` Joel Brobecker
2010-01-10 14:16 ` Hui Zhu
2010-06-21 15:05 ` Hui Zhu
2010-06-21 16:57 ` Joel Brobecker
2010-06-21 21:34 ` Joel Brobecker
2010-06-21 21:40 ` Tom Tromey
2010-06-22 7:29 ` Hui Zhu
2010-06-22 9:50 ` Pedro Alves
2010-06-22 15:21 ` Joel Brobecker
2010-06-22 18:05 ` Eli Zaretskii
2010-06-23 2:03 ` Hui Zhu
2010-06-23 16:59 ` Joel Brobecker
2010-06-24 6:13 ` Hui Zhu
2010-01-06 10:13 ` Eli Zaretskii
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=4B29018C.6060307@codesourcery.com \
--to=stan@codesourcery.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.com \
--cc=teawater@gmail.com \
--cc=tromey@redhat.com \
/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