From: Daniel Jacobowitz <drow@false.org>
To: "Frédéric Riss" <frederic.riss@gmail.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Make register_valid_p signed
Date: Mon, 24 Jul 2006 19:41:00 -0000 [thread overview]
Message-ID: <20060724194102.GC13612@nevyn.them.org> (raw)
In-Reply-To: <1153516549.5122.66.camel@funkylaptop>
On Fri, Jul 21, 2006 at 11:15:49PM +0200, Frédéric Riss wrote:
> The attached patch fixes this by declaring register_valid_p as a signed
> char array and also adds a comment (partly copied from the
> register_cached one).
Oops! Thank you. This patch is OK - you have write access, I think?
> While reading the code to find this out, I also noticed a little
> inconsistency. I don't really think this deserves a fix, but I thought
> I'd mention it anyway.
> Most people are using dwarf2 as debug format today, and with dwarf2
> symbols in registers are marked as LOC_COMPUTED. The read_var_value
> function will return NULL when a dwarf2 computed symbol needs access to
> a register that the target has marked as unavailable (register_valid_p <
> 0). This will make functions like print_frame_args output something like
> "my_var=???" for the unavailable var value.
> Yet if you use another debug format that marks the symbol as
> LOC_REGISTER, read_var_value will call error() if it can't read the
> register which is a lot more radical than the above behaviour.
You're right, this is a bit strange. Feel free to fix it if you like;
otherwise I'm sure it will eventually go away next time that code is
cleaned up thoroughly.
:REVIEWMAIL:
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-07-24 19:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-21 21:16 Frédéric Riss
2006-07-24 19:41 ` Daniel Jacobowitz [this message]
2006-07-24 20:17 ` Frédéric Riss
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=20060724194102.GC13612@nevyn.them.org \
--to=drow@false.org \
--cc=frederic.riss@gmail.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