Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Florian Hackenberger <f.hackenberger@chello.at>
To: gdb@sourceware.org, Paul Koning <pkoning@equallogic.com>
Subject: Re: breakpoints in shared libraries
Date: Tue, 14 Feb 2006 18:00:00 -0000	[thread overview]
Message-ID: <200602141859.25971.f.hackenberger@chello.at> (raw)
In-Reply-To: <17394.6343.166276.623893@gargle.gargle.HOWL>

On Tuesday 14 February 2006 18:52, you wrote:
> I did a hack solution as a local tweak to GDB 5.3 -- a few lines worth
> of change to set the "verbose" flag in the demangler calls.  That way,
> the several flavors of constructor and destructor end up with
> different names.  Odd ones, admittedly, but it allows them to be
> referenced individually.
Thank you very much indeed, but I just set breakpoints on every constructor 
call and resolved the underlying problem. Just for the sake of being able to 
set these breakpoints would not be worth the effort for patching and 
recompiling gdb.

Thanks anyway,
	Florian
-- 
Florian Hackenberger
student @
University of Technology
Graz, Austria
florian@hackenberger.at
www.hackenberger.at


  reply	other threads:[~2006-02-14 18:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-14 16:29 Florian Hackenberger
2006-02-14 17:00 ` Daniel Jacobowitz
2006-02-14 17:10   ` Florian Hackenberger
2006-02-14 17:13     ` Daniel Jacobowitz
2006-02-14 17:52       ` Paul Koning
2006-02-14 18:00         ` Florian Hackenberger [this message]
2006-02-14 17:21   ` Mark Kettenis
2006-02-14 17:23     ` Bob Rossi
2006-02-14 17:31     ` Daniel Jacobowitz
2006-02-14 17:47       ` Mark Kettenis
2006-02-14 17:08 ` Mark Kettenis
2006-02-14 17:20   ` Florian Hackenberger
  -- strict thread matches above, loose matches on Subject: below --
2001-11-13  9:05 Tom Tromey
2001-11-13  9:41 ` Daniel Jacobowitz
2001-11-13 10:11   ` Tom Tromey
2001-11-13 10:20 ` Per Bothner

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=200602141859.25971.f.hackenberger@chello.at \
    --to=f.hackenberger@chello.at \
    --cc=gdb@sourceware.org \
    --cc=pkoning@equallogic.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