From: Richard Sharpe <rsharpe@richardsharpe.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:13:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0212051738300.28669-100000@ns.aus.com> (raw)
In-Reply-To: <3DEFF716.2070803@redhat.com>
On Thu, 5 Dec 2002, 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.
The problem I saw was that it seemed that all of the routines that dealt
with evaluating variables were tuned to the printf command and writing
them to the output descriptor ... :-)
Regards
-----
Richard Sharpe, rsharpe[at]ns.aus.com, rsharpe[at]samba.org,
sharpe[at]ethereal.com, http://www.richardsharpe.com
prev parent reply other threads:[~2002-12-06 1:13 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
2002-12-05 17:13 ` Richard Sharpe [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=Pine.LNX.4.33.0212051738300.28669-100000@ns.aus.com \
--to=rsharpe@richardsharpe.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