This is the mail archive of the gdb-patches@sourceware.org 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: set print object on should affect MI varobjs (PR mi/13393)


> From: xgsa <xgsa@yandex.ru>
> Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
> Date: Sat, 31 Mar 2012 01:25:51 +0400
> 
> 31.03.2012, 00:52, "Eli Zaretskii" <eliz@gnu.org>:
> > Close, but not quite there yet.  The last piece we need to clarify is
> > the "actual (derived) type of the object is set" part.  What do you
> > mean by "type is set"?  This text describes the result returned by
> > '-var-create', so did you mean to say that the actual type is
> > mentioned in the tuple returned by this operation?  IOW, did you mean
> > to point out that the 'type=TYPE' part of -var-create's output will
> > mention the actual type as TYPE?
> 
> Yes, it is exactly what I meant. Can you help me with the better wording?

I suggest this:

  The varobj's type.  This is a string representation of the type, as
  would be printed by the @value{GDBN} CLI.  If @samp{print object}
  (@pxref{Print Settings, set print object}) is set to @code{on}, the
  @emph{actual} (derived) type of the object is shown rather than the
  @emph{declared} one.


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