From: "Eli Zaretskii" <eliz@gnu.org>
To: gdb@sources.redhat.com
Subject: Re: Variable "foo" is not available
Date: Fri, 08 Apr 2005 11:05:00 -0000 [thread overview]
Message-ID: <01c53c2a$Blat.v2.4$5c0bd720@zahav.net.il> (raw)
In-Reply-To: <20050402142639.GA27550@nevyn.them.org> (message from Daniel Jacobowitz on Sat, 2 Apr 2005 09:26:40 -0500)
> Date: Sat, 2 Apr 2005 09:26:40 -0500
> From: Daniel Jacobowitz <drow@false.org>
> Cc: gdb@sources.redhat.com, Reiner.Steib@gmx.de
>
> > I also find the string we print in this case too long. (You say that
> > in current CVS the output is a little nicer, but I don't see any
> > changes in CVS's dwarf2loc.c, which prints this, compared with GDB
> > 6.1; could you state in more detail which change you had in mind?)
>
> Only loclist_tracepoint_var_ref prints this message any more, assuming
> you are looking at a current version of the file.
>
> 2005-02-28 Daniel Jacobowitz <dan@codesourcery.com>
>
> * dwarf2loc.c (loclist_read_variable): Set optimized_out
> instead of reporting an error.
> * valprint.c (value_check_printable): New function.
> (common_val_print): New function. Use value_check_printable.
> (value_print): Use value_check_printable.
> * value.h (common_val_print): Add prototype.
So what message(s) or other effects would a user see with the current
CVS in situations such as the one Reiner described? I'm asking
because I want to amend the manual.
TIA
next prev parent reply other threads:[~2005-04-08 11:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-01 16:40 Reiner Steib
2005-04-01 17:19 ` Daniel Jacobowitz
2005-04-02 9:49 ` Eli Zaretskii
2005-04-02 13:53 ` Reiner Steib
2005-04-02 14:27 ` Daniel Jacobowitz
2005-04-06 16:25 ` Reiner Steib
2005-04-02 14:26 ` Daniel Jacobowitz
2005-04-02 18:17 ` Eli Zaretskii
2005-04-02 18:40 ` Daniel Jacobowitz
2005-04-02 20:58 ` Eli Zaretskii
2005-04-02 21:05 ` Daniel Jacobowitz
2005-04-04 5:14 ` Eli Zaretskii
2005-04-04 6:00 ` Mark Kettenis
2005-04-04 7:58 ` Daniel THOMPSON
2005-04-04 19:28 ` Eli Zaretskii
2005-04-04 13:37 ` Daniel Jacobowitz
2005-04-04 19:35 ` Eli Zaretskii
2005-04-04 19:41 ` Daniel Jacobowitz
2005-04-03 18:16 ` Reiner Steib
2005-04-08 11:05 ` Eli Zaretskii [this message]
2005-04-04 9:26 ` Reiner Steib
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='01c53c2a$Blat.v2.4$5c0bd720@zahav.net.il' \
--to=eliz@gnu.org \
--cc=gdb@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