Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@zwingli.cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Nick Duffek <nsd@redhat.com>,
	ezannoni@cygnus.com, gdb-patches@sources.redhat.com,
	taylor@candd.org
Subject: Re: [RFA] findvar.c: support LOC_BASEREG[_ARG] on Harvard archs
Date: Mon, 16 Jul 2001 15:59:00 -0000	[thread overview]
Message-ID: <npofqkxywb.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: <3B536F7B.7060106@cygnus.com>

Andrew Cagney <ac131313@cygnus.com> writes:

> 
> 
> >> -	char *buf = (char*) alloca (MAX_REGISTER_RAW_SIZE);
> >> +	value_ptr regval;
> 
> 
> value_ptr is really ``struct value *'' so ...
> 
> 
> >> +	regval = value_from_register (lookup_pointer_type (type),
> >> +				      SYMBOL_BASEREG (var), frame);
> >> +	if (regval == NULL)
> >> +	  error ("Value of base register not available.");
> >> +	addr = value_as_pointer (regval);
> 
> 
> I suspect you need xfree() or the like.

No --- all values get put in a global list, `all_values', which gets
freed automatically when the current expression evaluation is complete.
Grep for `all_values' and see how it gets used.


  reply	other threads:[~2001-07-16 15:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-16 10:13 Nick Duffek
2001-07-16 11:29 ` Jim Blandy
2001-07-16 14:35   ` Nick Duffek
     [not found]     ` <npsnfwy0u8.fsf@zwingli.cygnus.com>
2001-07-16 15:49       ` Andrew Cagney
2001-07-16 15:59         ` Jim Blandy [this message]
2001-07-16 16:13         ` Nick Duffek
2001-07-16 15:59       ` Nick Duffek
2001-07-16 16:09         ` Andrew Cagney
2001-07-16 16:13           ` Nick Duffek
2001-07-16 16:17           ` Nick Duffek
     [not found] ` <3B535097.5040106@cygnus.com>
2001-07-16 14:16   ` Jim Blandy

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=npofqkxywb.fsf@zwingli.cygnus.com \
    --to=jimb@zwingli.cygnus.com \
    --cc=ac131313@cygnus.com \
    --cc=ezannoni@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=nsd@redhat.com \
    --cc=taylor@candd.org \
    /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