Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Mark Santcroos <marks@ripe.net>
Cc: gdb@sources.redhat.com
Subject: Re: add-symbol-file parsing
Date: Mon, 02 Dec 2002 21:29:00 -0000	[thread overview]
Message-ID: <20021203052939.GA22983@nevyn.them.org> (raw)
In-Reply-To: <20021129105448.GF598@laptop.6bone.nl>

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?

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-12-03  5:29 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 [this message]
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

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=20021203052939.GA22983@nevyn.them.org \
    --to=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