Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Variable objects: references formatting
Date: Thu, 04 May 2006 07:20:00 -0000	[thread overview]
Message-ID: <17497.43822.261192.673547@farnswood.snap.net.nz> (raw)
In-Reply-To: <200605041100.09748.ghost@cs.msu.su>

 > Well, if you say patches against the previous revision of a file cause 
 > problems, I'll try to send patches against most current version in future.

Thanks.

 ...
 > > No, I just didn't appreciate the difference between pointers and references
 > > in GDB.  The discrepancy I "found" was due to me mistyping.  However I do
 > > see a problem with gcc 4.1 and variable objects where GDB keeps telling me:
 > >
 > >    Child of parent whose type does not allow children
 > >
 > > when it didn't when my program was compiled with gcc 3.2.
 > 
 > Again, maybe you can provide specific case where this error is produced? If
 > it affect real-world cases we'd better fix it soon.

It happens when I debug Emacs but I can't provide a simple case yet.  
However, do you see the problem with references that I mentioned earlier
(that they don't seem to disappear from the changelist with -var-update)?
This seems to be the case for any variable object made from a reference.

-- 
Nick                                           http://www.inet.net.nz/~nickrob


  reply	other threads:[~2006-05-04  7:20 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2006-05-04 12:10         ` Vladimir Prus
2006-05-08 12:41           ` [PATCH] -var-update [was Re: Variable objects: references formatting] Nick Roberts
2006-05-08 17:27             ` Jim Blandy
2006-05-08 21:17               ` Nick Roberts
2006-05-15 16:54             ` Daniel Jacobowitz
2006-05-17  0:45               ` Nick Roberts
2006-05-17  1:28                 ` Daniel Jacobowitz
2006-05-17  1:43                   ` Nick Roberts
2006-05-17  3:39                     ` Daniel Jacobowitz
2006-05-19  7:41                       ` [PATCH] -var-update Nick Roberts
2006-05-19  9:47                         ` Vladimir Prus
  -- strict thread matches above, loose matches on Subject: below --
2006-05-03  9:22 Variable objects: references formatting Vladimir Prus
2006-05-03 17:50 ` Jim Blandy
2006-05-03 18:08   ` Jim Blandy
2006-05-04  5:19     ` Vladimir Prus
2006-05-04  6:08       ` Jim Blandy
2006-05-04  6: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=17497.43822.261192.673547@farnswood.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --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