From: Jason Merrill <jason@redhat.com>
To: gdb-patches@sources.redhat.com
Cc: gcc@gcc.gnu.org
Subject: Re: [RFA/stabs reader] Fix v3 duplicate constructors problem
Date: Mon, 03 Dec 2001 14:58:00 -0000 [thread overview]
Message-ID: <wvln10zewwg.fsf@prospero.cambridge.redhat.com> (raw)
In-Reply-To: <20011203172931.A2512@nevyn.them.org> (Daniel Jacobowitz's message of "Mon, 3 Dec 2001 17:29:31 -0500")
>>>>> "Daniel" == Daniel Jacobowitz <drow@mvista.com> writes:
>> What does GDB actually use the member function information for? What
>> impact would this change have, other than the output of ptype?
> Right now, the big thing is probably member function calls. If the
> constructor is called from GDB, we want to get the complete object
> constructor. I'm not 100% sure this is even possible, though.
You can't call a constructor directly in C++; no reason to allow it from
GDB. Destructors are a different matter, though; an explicit call should
go to the non-deleting, in-charge version.
> I hadn't considered setting breakpoints on all of them. That's very
> difficult; suppose I look at an assembly listing for a constructor and
> tell it to break on a particular line. How can I figure out source
> line information for every constructor?
With Dwarf, all clones/inlines point to the abstract version; the internal
representation could keep track of all instances of a particular abstract
function.
> Perhaps it is best to continue emitting them and ignore them until we
> support them in GDB.
Seems reasonable.
Jason
next prev parent reply other threads:[~2001-12-03 22:58 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 [this message]
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
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=wvln10zewwg.fsf@prospero.cambridge.redhat.com \
--to=jason@redhat.com \
--cc=gcc@gcc.gnu.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).