Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pierre Muller <muller@cerbere.u-strasbg.fr>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA 2nd try] tell in which register a register var is loaded.
Date: Wed, 28 Nov 2001 07:52:00 -0000	[thread overview]
Message-ID: <4.2.0.58.20011128164610.00a45da0@ics.u-strasbg.fr> (raw)
Message-ID: <20011128075200.9rksxps2vlPNDLsltOaKA2dWD7k75Rhq9XXesd8x1uY@z> (raw)
In-Reply-To: <3C045C10.3020902@cygnus.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1635 bytes --]

At 04:37 28/11/2001 , Andrew Cagney a écrit:
>>This patch superseeds the previous one,
>>the lval_reg_frame_relative case was not handled correctly there.
>> http://sources.redhat.com/ml/gdb-patches/2001-11/msg00301.html
>>
>>Still no idea who should give an approval for this patch ?
>
>No one else did so ...
>
>>2001-11-20 Pierre Muller  <muller@ics.u-strasbg.fr>
>>     * findvar.c (locate_var_value): specify in which register a register
>>     variable is stored.
>
>Don't forget to ucase ``specify''.
>
>Hmm, can REGISTER_NAME (num) ever be invalid or is this just being careful?
>
>If the latter then can I suggest an assertion vis:
>
>         gdb_assert (REGISTER_NAME (...) != NULL
>                     && *REGISTER_NAME (...) != '\0');
>
>If the former then the test will need to be tweeked to check for both NULL and '\0'.
>
>Your choice.

Looking at different places where REGISTER_NAME is used, it seems to be 
almost always assumed that it is valid, so I will probably simply remove the check.

>I don't think the ``$'' prefix is consistent with existing code - based mainly on a quick grep that didn't reveal any code doing this.  (I don't actually have anything agains the convention though - just a separate change :-)

Look at tracepoint.c around line 2380 in function scope_info
and you will find lots of GDB code using printf_filtered("... in register $%s",REGISTER_NAME(...))

>Otherwize, yes, a much more helpful error message.



Pierre Muller
Institut Charles Sadron
6,rue Boussingault
F 67083 STRASBOURG CEDEX (France)
mailto:muller@ics.u-strasbg.fr
Phone : (33)-3-88-41-40-07  Fax : (33)-3-88-41-40-99


  parent reply	other threads:[~2001-11-28  7:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-08  7:24 Pierre Muller
2001-11-27 19:37 ` Andrew Cagney
2001-11-15 10:53   ` Andrew Cagney
2001-11-16 14:19   ` Pierre Muller [this message]
2001-11-28  7:52     ` Pierre Muller
2001-11-28 11:27     ` Andrew Cagney
2001-11-17 17:22       ` Andrew Cagney

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=4.2.0.58.20011128164610.00a45da0@ics.u-strasbg.fr \
    --to=muller@cerbere.u-strasbg.fr \
    --cc=ac131313@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    /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