From: Michael Chastain <mec.gnu@mindspring.com>
To: jimb@redhat.com, david.carlton@sun.com
Cc: gdb@sources.redhat.com
Subject: Re: representing C++ constructors in GDB's symbol tables
Date: Sat, 18 Sep 2004 02:29:00 -0000 [thread overview]
Message-ID: <414B9D8B.nailB2O11AVBZ@mindspring.com> (raw)
In-Reply-To: <yf2ekl0a0ra.fsf@kealia.sfbay.sun.com>
David Carlton <david.carlton@sun.com> wrote:
> You can use "X(...)" to create a temporary object of type X.
Sure. And of course:
X my_x = X();
Also remember destructors. A C++ program can explicitly call
a destructor. Sigh.
> Having said that, a constructor really is a different beast from an
> ordinary function call. And I don't think that having GDB support
>
> (gdb) print Printer().print()
>
> should be high on your list of priorities.
Yeah. I would be comfortable if gdb said "forget about it,
I don't call a ctor directly" (and the same for dtor).
Then in 2006 someone else can come along and fix that limitation,
watching out for the big trap that the ABI for constructors and
destructors can be *different* than for normal functions,
with hidden magic parameters.
Michael
next prev parent reply other threads:[~2004-09-18 2:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-17 22:46 Jim Blandy
2004-09-18 0:14 ` Daniel Jacobowitz
2004-09-18 0:18 ` David Carlton
2004-09-18 2:29 ` Michael Chastain [this message]
2004-09-20 16:36 ` David Carlton
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=414B9D8B.nailB2O11AVBZ@mindspring.com \
--to=mec.gnu@mindspring.com \
--cc=david.carlton@sun.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@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