From: Michael Snyder <msnyder@specifix.com>
To: Yakov Lerner <iler.ml@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: implementing eval command
Date: Tue, 19 Feb 2008 19:12:00 -0000 [thread overview]
Message-ID: <1203448086.19253.153.camel@localhost.localdomain> (raw)
In-Reply-To: <f36b08ee0802152336u20ee54earaf645e194ffae5b8@mail.gmail.com>
On Sat, 2008-02-16 at 09:36 +0200, Yakov Lerner wrote:
> On Fri, Feb 15, 2008 at 7:58 PM, Michael Snyder <msnyder@specifix.com> wrote:
> > Moving this to "gdb" list, since it is not a patch.
> >
> >
> >
> > On Thu, 2008-02-14 at 18:18 +0200, Yakov Lerner wrote:
> > > I'd like to make a patch that implements eval command, as follows.
> > > I have following idea to implement eval simply:
> > > Syntax of eval will be similar to the syntax of 'printf' command:
> > > eval "string with %..." comma-separated-expressions
> > > Implementation relies on existing printf_command() function,
> > > by rewriting printf_command into pair of functions, one that computes
> > > result of printf as allocated string; both printf_command and eval_command
> > > will use compute_printf() function.
> > > What do you think ?
> >
> > Hmmm, that would be one way of getting around the
> > limitations of some commands that can't accept expressions
> > as arguments (mentioned in another thread).
> >
> > What do you see as the context for this eval command?
> > How do you imagine it will be used?
>
> Apparently, the capability to insert variable into arbitrary part of
> gdb command is missing in gdb. I hit this several days ago when I needed
> to make a script that uses 'thread apply $num where' to a subset of threads
> in a program that had hundreds of threads and I was told on the list that this
> is impossible.
Oh yes, that was the thread I was thinking about.
> I also see other requests for eval command on the mailing list archive.
> So, instead of enriching just 'thread apply' command to accept variable
> (or maybe parenthesized expression) I thought it's much more generic
> to have eval command in the end.
>
> I thought about easy way to implement it, and then I got idea of using
> the print-like format and comma-separated arg list.
Cool, well, personally I think this is a very interesting idea.
With the printf format, it should be possible to construct
fairly complex commands.
prev parent reply other threads:[~2008-02-19 19:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f36b08ee0802140818j2c5d26d5yb09c3662b81f8444@mail.gmail.com>
2008-02-15 17:59 ` Michael Snyder
2008-02-16 7:37 ` Yakov Lerner
2008-02-19 19:12 ` Michael Snyder [this message]
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=1203448086.19253.153.camel@localhost.localdomain \
--to=msnyder@specifix.com \
--cc=gdb@sourceware.org \
--cc=iler.ml@gmail.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