Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@arm.com>
To: Michael Snyder <msnyder@redhat.com>
Cc: Daniel Jacobowitz <drow@mvista.com>,
	Richard.Earnshaw@arm.com, gdb-patches@sources.redhat.com
Subject: Re: Infinite loop in make_cv_type
Date: Fri, 22 Feb 2002 09:41:00 -0000	[thread overview]
Message-ID: <200202221740.RAA00732@cam-mail2.cambridge.arm.com> (raw)
In-Reply-To: Your message of "Fri, 22 Feb 2002 09:18:46 PST." <3C767D76.11C6@redhat.com>

> Daniel Jacobowitz wrote:
> > 
> > On Fri, Feb 22, 2002 at 11:40:38AM +0000, Richard Earnshaw wrote:
> > > While testing cplusfuncs.exp on ARM/NetBSD (a.out) with gcc-3 current, gdb
> > > is getting stuck in an infinite loop in gdbtypes.c:make_cv_type and I'm
> > > trying to work out what this is supposed to do.  The scenario I'm seeing
> > > is that the type ring has become corrupted as follows along the
> > > TYPE_CV_TYPE chain
> > >
> > >           type
> > >           |
> > >             V
> > >         var1<----+
> > >             |      |
> > >             +------+
> > >
> > > Given that this is supposed to be a loop, it's clearly bogus.
> > 
> > Definitely.
> 
> Hang on, I'm pretty sure that the cv type chain
> is supposed to do that.  The pointer loop is 
> intentional.

Well if that's the case then the top loop in make_cv_type is completely 
bogus, since it expects to iterate until ntype==type (where type is the 
base type).

The comment in gdbtypes.h says that cv_type is a ring of the type and its 
variants.

R.


  reply	other threads:[~2002-02-22 17:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-22  3:41 Richard Earnshaw
2002-02-22  7:55 ` Daniel Jacobowitz
2002-02-22  9:24   ` Michael Snyder
2002-02-22  9:41     ` Richard Earnshaw [this message]
2002-02-22 10:33     ` Daniel Jacobowitz
2002-02-22 10:22   ` Richard Earnshaw
2002-02-22 10:38     ` Daniel Jacobowitz
2002-02-22 10:46       ` Richard Earnshaw
2002-02-22 11:07         ` Richard Earnshaw
2002-02-22 11:45           ` Richard Earnshaw
2002-02-22 11:52             ` Daniel Jacobowitz

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=200202221740.RAA00732@cam-mail2.cambridge.arm.com \
    --to=rearnsha@arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=msnyder@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