Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@gnu.org>
To: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
Cc: drow@false.org, gdb@sources.redhat.com, rolandz@poczta.fm
Subject: Re: How to setup a breakpoint on constructor
Date: Sat, 17 Jul 2004 14:30:00 -0000	[thread overview]
Message-ID: <5567-Sat17Jul2004132833+0300-eliz@gnu.org> (raw)
In-Reply-To: <20040716193117.EFE514B104@berman.michael-chastain.com> (mec.gnu@mindspring.com)

> Date: Fri, 16 Jul 2004 15:31:17 -0400 (EDT)
> From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
> 
> To take the points in reverse order,
> 
> > (B) It exposes the difference between complete and base constructors,
> > which is an implementation detail of the C++ ABI that most users don't
> > understand.
> 
> That is reality.

Yes.

> The reality is that g++ emits two functions in the object code.  In
> my opinion, if we try to gloss over that, then we'll just create
> more confusion for commands such as 'disassemble' and 'tbreak'.

We could perhaps help users who are oblivious to this (or just
forgot) by showing them the possible places where GDB could put the
breakpoint, including the more self-explaining names, and asking them
what to do.  For example:

    (gdb) break 'A::A()'
    The constructor 'A::A()' has two code instances:

      Address    Mangled Name   Name               Description
      08048544   _ZN1AC1Ev      A::A()$base()      Base constructor for A
      080486e2   _ZN1AC2Ev      A::A()$allocate()  Allocating constructor for A

    Where do you want to put your breakpoint?  Type `1' for the first
    instance, `2' for the second, `A' for all of them:
    1 <==== user response

    Breakpoint 1 at 0x8048544: file derivation.cc, line 7.


  parent reply	other threads:[~2004-07-17 10:30 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-16 19:59 Michael Elizabeth Chastain
2004-07-16 22:15 ` Jim Blandy
2004-07-17 14:30 ` Eli Zaretskii [this message]
2004-07-17 14:54   ` Daniel Jacobowitz
  -- strict thread matches above, loose matches on Subject: below --
2004-07-18 19:29 Michael Elizabeth Chastain
2004-07-19  3:58 ` Eli Zaretskii
2004-07-17 23:17 Michael Elizabeth Chastain
2004-07-18  5:05 ` Eli Zaretskii
2004-07-18 18:44   ` Daniel Jacobowitz
2004-07-18 19:03     ` Eli Zaretskii
2004-07-19  3:22       ` Daniel Jacobowitz
2004-07-19 14:51         ` Eli Zaretskii
2004-07-17 10:09 Michael Elizabeth Chastain
2004-07-15 13:55 Michael Elizabeth Chastain
2004-07-15 14:09 ` Daniel Jacobowitz
2004-07-16 11:11   ` Eli Zaretskii
2004-07-16 14:27     ` Daniel Jacobowitz
2004-07-17 10:30       ` Eli Zaretskii
2004-07-15 11:31 Michael Elizabeth Chastain
2004-07-16 13:17 ` Roland Zerek
2004-07-15 10:30 Roland Zerek

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=5567-Sat17Jul2004132833+0300-eliz@gnu.org \
    --to=eliz@gnu.org \
    --cc=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=mec.gnu@mindspring.com \
    --cc=rolandz@poczta.fm \
    /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