From: Daniel Jacobowitz <drow@mvista.com>
To: Fernando Nasser <fnasser@redhat.com>
Cc: Mark Santcroos <marks@ripe.net>, gdb@sources.redhat.com
Subject: Re: add-symbol-file parsing
Date: Thu, 05 Dec 2002 17:10:00 -0000 [thread overview]
Message-ID: <20021206011053.GA28778@nevyn.them.org> (raw)
In-Reply-To: <3DEFF716.2070803@redhat.com>
Mostly as a workaround for this...
Which would you prefer - changing add-symbol-file or a more general
eval command? What would you think natural to evaluate - just
convenience variables? Parsing expressions out of such a thing is hard
in the general case. Hmm... we could allow (EXPR), i.e. require the
parentheses.
Honestly, rather than adding an eval command, I'd prefer to see $var
and (EXPR) accepted _everywhere_ the CLI looks for an integer. Some
unified functions to parse command lines is all it would take.
On Thu, Dec 05, 2002 at 08:02:14PM -0500, Fernando Nasser wrote:
> We have been talking of an eval command in another thread that would also
> solve this problem.
>
> eval add-symbol-file /dir/symbol.file $text_addr
>
> would cause
>
> add-symbol-file /dir/symbol.file 0xdeadc0de
>
> to be executed.
>
>
> Fernando
>
> --
> Fernando Nasser
> Red Hat - Toronto E-Mail:
>
> Mark Santcroos wrote:> Hi Daniel,
> >
> >On Tue, Dec 03, 2002 at 12:29:39AM -0500, Daniel Jacobowitz wrote:
> >
> >>The problem is, add-symbol-file takes more than a $text_addr. It also
> >>takes a series of -s SECNAME $sec_addr. We could:
> >>
> >>- split the command line at -s options and parse anything before the
> >> next -s option as an expression, assuming people will not foolishly
> >> use -s in their expression;
> >>- allow only convenience variables
> >>
> >>Option 2 may be the way to go... What do others think about allowing
> >>integer-or-convenience-variable there?
> >
> >
> >Option 2 would at least enable us to do everything. In the worst case you
> >would have to add another line to your macro that does the
> >expression-to-convinience-variable-translation.
> >
> >Please let me know if you don't have time and would prefer me to tackle
> >this.
> >
> >Thanks
> >
> >Mark
> >
>
>
> @redhat.com
> 2323 Yonge Street, Suite #300
> Toronto, Ontario M4P 2C9
>
>
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-12-06 1:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-29 2:54 Mark Santcroos
2002-12-02 21:29 ` Daniel Jacobowitz
2002-12-02 21:43 ` Richard Sharpe
2002-12-02 23:49 ` Mark Santcroos
2002-12-05 17:02 ` Fernando Nasser
2002-12-05 17:10 ` Daniel Jacobowitz [this message]
2002-12-05 17:13 ` Richard Sharpe
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=20021206011053.GA28778@nevyn.them.org \
--to=drow@mvista.com \
--cc=fnasser@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=marks@ripe.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