Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Jim Blandy" <jimb@red-bean.com>
To: "Vladimir Prus" <ghost@cs.msu.su>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Variable objects: references formatting
Date: Wed, 03 May 2006 18:08:00 -0000	[thread overview]
Message-ID: <8f2776cb0605031108j2371fd7dodcc9f6cecf305c5d@mail.gmail.com> (raw)
In-Reply-To: <8f2776cb0605031050q6b9f1b2ale98d0734d4dec3f9@mail.gmail.com>

On 5/3/06, Jim Blandy <jimb@red-bean.com> wrote:
> On 5/3/06, Vladimir Prus <ghost@cs.msu.su> wrote:
> > At the moment, when using variable objects to display a struct or a class,
> > the result of -data-evaluate-expression is "...". However, when displaying
> > a reference to a class, the result of -data-evaluate-expression is
> > {}-enclosed list of members and their values.
> >
> > This disparity does not seem to be reasonable, the attached patch fixes it:
>
> I think you're right, and the patch looks good.  I'll apply it.

Some further stuff I came across, for future reference:

- ChangeLog entries need to have two spaces between the date and the
name, and the name and the email address.  They need an asterisk
before the filename.  Check out the other ChangeLog entries for
examples.

- When declaring a pointer to a type, GNU coding style writes 'type
*ptr', not 'type* ptr'.

- In GDB, when traversing types, remember to call check_typedef to
avoid having your traversal stopped by typedef nodes.


  reply	other threads:[~2006-05-03 18:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-03  9:22 Vladimir Prus
2006-05-03 17:50 ` Jim Blandy
2006-05-03 18:08   ` Jim Blandy [this message]
2006-05-04  5:19     ` Vladimir Prus
2006-05-04  6:08       ` Jim Blandy
2006-05-04  6:10         ` Vladimir Prus
2006-05-03 23:05 Nick Roberts
2006-05-03 23:50 ` Jim Blandy
2006-05-04  1:53   ` Nick Roberts
2006-05-04 17:32     ` Jim Blandy
2006-05-04 22:30       ` Nick Roberts
2006-05-05  8:08         ` Jim Blandy
2006-05-04  5:30 ` Vladimir Prus
2006-05-04  6:21   ` Nick Roberts
2006-05-04  7:00     ` Vladimir Prus
2006-05-04  7:20       ` Nick Roberts
2006-05-04 12:10         ` Vladimir Prus

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=8f2776cb0605031108j2371fd7dodcc9f6cecf305c5d@mail.gmail.com \
    --to=jimb@red-bean.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=ghost@cs.msu.su \
    /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