This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Variable "foo" is not available


> 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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]