From: Joe Buck <jbuck@synopsys.COM>
To: jimb@zwingli.cygnus.com (Jim Blandy)
Cc: jason@redhat.com (Jason Merrill),
msnyder@cygnus.com (Michael Snyder),
gdb-patches@sources.redhat.com, gcc@gcc.gnu.org
Subject: Re: [RFA/stabs reader] Fix v3 duplicate constructors problem
Date: Tue, 04 Dec 2001 09:43:00 -0000 [thread overview]
Message-ID: <200112041742.JAA27724@atrus.synopsys.com> (raw)
In-Reply-To: <npwv037wnl.fsf@zwingli.cygnus.com> from "Jim Blandy" at Dec 04, 2001 11:55:10 AM
>
>
> Jason Merrill <jason@redhat.com> writes:
> > 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.
>
> Wouldn't it be reasonable for GDB to support `new' expressions?
Yes, if the gdb user can call placement new, s/he can call a constructor
and place an object whereever desired. Something like
(gdb) call new(ptr) SomeClass(1, "Hello")
next prev parent reply other threads:[~2001-12-04 17:43 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
2001-12-04 8:53 ` Jim Blandy
2001-12-04 9:43 ` Joe Buck [this message]
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=200112041742.JAA27724@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jason@redhat.com \
--cc=jimb@zwingli.cygnus.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).