Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <mec@shout.net>
To: drow@mvista.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/c++testsuite] New test for constructor breakpoints
Date: Sat, 16 Feb 2002 11:11:00 -0000	[thread overview]
Message-ID: <200202161911.g1GJBL711737@duracef.shout.net> (raw)

Hi Daniel,

> The patch tests _overloaded_ constructors.

Ah, you are right.  I saw the choice menu and jumped to an incorrect
conclusion about what you were doing.  I'll revisit the patch.

> The bug, however, is with
> _cloned_ constructors.  Not the same thing at all.  Cloned constructors
> are not user-visible objects; they only differ in that they use
> different offsets into the object based on whether it is a baseclass or
> the principal object.

But the cloned constructor is visible.  For instance, suppose Foo is
a virtual base class, and suppose Foo::Foo calls other functions,
and suppose that I set a breakpoint on another function.  Then the
not-in-charge version of Foo::Foo is on the stack and it is going to
appear to the user with *some* name.

I would like to show this as Foo::Foo$nic, and I would like the user to
be able to set breakpoints on either Foo::Foo or Foo::Foo$nic or both,
as they see fit.

Michael C


             reply	other threads:[~2002-02-16 19:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-16 11:11 Michael Elizabeth Chastain [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-19 16:04 Michael Elizabeth Chastain
2002-02-19 16:12 ` Daniel Jacobowitz
2002-02-18 12:26 Michael Elizabeth Chastain
2002-02-18 13:17 ` Daniel Jacobowitz
2002-02-19 15:35 ` Daniel Jacobowitz
2002-02-15 16:50 Michael Elizabeth Chastain
2002-02-15 18:28 ` Daniel Jacobowitz
2002-02-14 15:32 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=200202161911.g1GJBL711737@duracef.shout.net \
    --to=mec@shout.net \
    --cc=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