From: Richard Sharpe <rsharpe@richardsharpe.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Mark Santcroos <marks@ripe.net>, <gdb@sources.redhat.com>
Subject: Re: add-symbol-file parsing
Date: Mon, 02 Dec 2002 21:43:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0212022208011.15616-100000@ns.aus.com> (raw)
In-Reply-To: <20021203052939.GA22983@nevyn.them.org>
On Tue, 3 Dec 2002, Daniel Jacobowitz wrote:
> On Fri, Nov 29, 2002 at 11:54:48AM +0100, Mark Santcroos wrote:
> > Unlike the documentation says the 'address' argument to 'add-symbol-file'
> > is not parsed as an expression but directly as an address.
> >
> > The following commands ...
> >
> > (gdb) set $text_addr = 0xdeadc0de
> > (gdb) add-symbol-file /dir/symbol.file $text_addr
> >
> > .. will end up setting the address to 0 by strtoul down in the code path.
> >
> > The above will therefor not work. Is there another way I can achieve this?
> >
> > If this is not possible (in another way) will patches be accepted to make
> > this an expression?
>
> 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?
I would love to be able to use convenience variables for the file name and
the text_addr. I started looking at it in 5.2.1, but quickly got bogged
down in a twisty maze of code.
Regards
-----
Richard Sharpe, rsharpe[at]ns.aus.com, rsharpe[at]samba.org,
sharpe[at]ethereal.com, http://www.richardsharpe.com
next prev parent reply other threads:[~2002-12-03 5:43 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 [this message]
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
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.0212022208011.15616-100000@ns.aus.com \
--to=rsharpe@richardsharpe.com \
--cc=drow@mvista.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