Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Doug Evans <dje@google.com>
Cc: gdb <gdb@sourceware.org>
Subject: Re: constructor breakpoints
Date: Sun, 30 Mar 2008 21:26:00 -0000	[thread overview]
Message-ID: <20080328025108.GA3529@caradoc.them.org> (raw)
In-Reply-To: <e394668d0803271704h7bc1423cm3edb22097f3f3045@mail.gmail.com>

On Thu, Mar 27, 2008 at 05:04:57PM -0700, Doug Evans wrote:
> Having recently tripped over this (not being able to set breakpoints
> on constructors), and having read as much of the sordid history of
> this as I can find, I wonder what the current thinking is on how to
> fix this.  Has there been any progress?

Not that I know of.  Hey, at least we fixed the _other_ breakpoints in
constructors bug.

> The ?HERE's are because symbol lookup finds the class, not the
> constructor.  Being able to specifically ask for the constructor seems
> like a reasonable way to go.  This could be done by encoding the
> request in the name (looking up c::c), or specifying the class of
> object to lookup (e.g. LOC_BLOCK), or rearranging the symbol table
> such that one can lookup the class, and then from that lookup (or
> iterate) over members that match certain parameters.  [I'm just
> throwing out a range of possibilities.]

I like that last one - I always have - but I'm a little worried about
how much work it would be in practice; neither stabs nor dwarf symbol
info is really laid out quite right for it.

-- 
Daniel Jacobowitz
CodeSourcery


      reply	other threads:[~2008-03-28  2:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-28 15:41 Doug Evans
2008-03-30 21:26 ` Daniel Jacobowitz [this message]

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=20080328025108.GA3529@caradoc.them.org \
    --to=drow@false.org \
    --cc=dje@google.com \
    --cc=gdb@sourceware.org \
    /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