Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] gdb.c++/templates.exp, pr gdb/1063
Date: Wed, 26 Feb 2003 00:34:00 -0000	[thread overview]
Message-ID: <20030226003426.GA32574@nevyn.them.org> (raw)
In-Reply-To: <ro1n0kjubmi.fsf@jackfruit.Stanford.EDU>

On Tue, Feb 25, 2003 at 04:30:29PM -0800, David Carlton wrote:
> On Tue, 25 Feb 2003 19:15:36 -0500, Daniel Jacobowitz <drow@mvista.com> said:
> 
> > Note that we can't print out the above in stabs or dwarf-2; neither of
> > them puts the abstract type in the debug info, only the referenced
> > type.  DWARF-2 can say a bit more than it does now - specifically, that
> > "int" is a template paramater for C - but "DWARF does not represent the
> > generic template definition, but does represent each instantiation"
> > according to the v3 draft.
> 
> Thanks for the info; I hadn't gotten around to looking at the relevant
> parts of the DWARF standard yet.
> 
> > The reason we often print out one of the instantiations is because each
> > C<T> contains a nested typedef for C in the DWARF-2.  We don't handle
> > nested types right yet.
> 
> Ah.  Hmm.  Why does it contain a nested typedef for C?  I guess that
> makes sense: 14.6p2 gives an example of how you can use C to refer to
> C<T> within the definition of C<T>.
> 
> In that case, I don't think that the desire of the original test case
> (i.e. printing out actual template info) is reasonable: it's not the
> job of GDB's test suite to lobby for improvements in debugging
> formats.  So I think the proper behavior is to delete the original
> success regexps, to decide that, in this situation, GDB shouldn't
> print out any information (which is what currently happens with GCC
> 2.95.3/stabs), to KFAIL the situations where it does print out an
> instantiation with reference to a PR about nested classes (I assume we
> have such a PR, if not I'll create one), and to close PR 1063 with an
> appropriate comment.
> 
> How does that sound?

Or run the test only for HP, which _does_ have this information.

Does any of the code still work?  I've got no idea.  I only ran the C
testsuites on HP/UX, not the C++ ones.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-02-26  0:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-26  0:35 David Carlton
2003-02-26  0:15 ` Daniel Jacobowitz
2003-02-26  1:35   ` David Carlton
2003-02-26  0:34     ` Daniel Jacobowitz [this message]
2003-02-26  1:03       ` David Carlton
2003-02-26 20:27         ` David Carlton
2003-02-26  1:15 Michael Elizabeth Chastain
2003-02-26  1:23 ` David Carlton
2003-02-26  2:00 Michael Elizabeth Chastain

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=20030226003426.GA32574@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.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