From: Jason Merrill <jason@redhat.com>
To: Michael Snyder <msnyder@cygnus.com>
Cc: gdb-patches@sources.redhat.com, gcc@gcc.gnu.org
Subject: Re: [RFA/stabs reader] Fix v3 duplicate constructors problem
Date: Tue, 04 Dec 2001 08:25:00 -0000 [thread overview]
Message-ID: <wvlitbncksk.fsf@prospero.cambridge.redhat.com> (raw)
In-Reply-To: <3C0C0A1F.E9274328@cygnus.com> (Michael Snyder's message of "Mon, 03 Dec 2001 15:26:23 -0800")
>>>>> "Michael" == Michael Snyder <msnyder@cygnus.com> writes:
> Jason Merrill wrote:
>> You can't call a constructor directly in C++; no reason to allow it from
>> GDB.
> OTOH, there are a lot of things that you can do from GDB
> that you cannot do programmatically. Accessing private data
> would be an example. Since GDB can call any other function,
> is there a strong reason why it should not be able to call
> the constructors?
Constructors and destructors have traditionally had a special calling
convention. Though I suppose that as of v3, we've gone to clones rather
than extra hidden parameters, so it would be more feasible to allow users
to call them directly from the debugger. In any case, it needs some sort
of special handling.
Jason
next prev parent reply other threads:[~2001-12-04 16:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20011203154836.A28821@nevyn.them.org>
2001-12-03 13:52 ` Jason Merrill
2001-12-03 14:29 ` Daniel Jacobowitz
2001-12-03 14:58 ` Jason Merrill
2001-12-03 15:25 ` Michael Snyder
2001-12-04 8:25 ` Jason Merrill [this message]
2001-12-04 8:53 ` Jim Blandy
2001-12-04 9:43 ` Joe Buck
2001-12-04 1:09 Michael Elizabeth Chastain
2001-12-04 5:27 ` Jason Merrill
2001-12-04 7:40 ` Daniel Berlin
2001-12-04 8:58 ` 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=wvlitbncksk.fsf@prospero.cambridge.redhat.com \
--to=jason@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).