Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Anton MOUKHARSKI <anton.moukharski@cea.fr>
Cc: gdb@sourceware.org
Subject: Re: Breakpoint not hit because of function pointers or something similar
Date: Mon, 10 May 2010 19:27:00 -0000	[thread overview]
Message-ID: <m3hbmfblsf.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4BE01FC1.8050309@cea.fr> (Anton MOUKHARSKI's message of "Tue, 04	May 2010 15:23:13 +0200")

>>>>> "Anton" == Anton MOUKHARSKI <anton.moukharski@cea.fr> writes:

Anton> I am trying to hit a breakpoint that appears early in the code, but
Anton> gdb (ddd) misses it each time. At first I thought it was because of
Anton> templates, but gdb seems to cope with that. I have a code similar to
Anton> this one (C++, don't read it in detail at first) :

It would be helpful if you mentioned your gdb version, your platform,
and exactly what you tried in gdb.

Anton> So is there anyway to tell gdb that I don't wan't a breakpoint
Anton> relative to a linenumber in a source file or a simple function name
Anton> but to the instance of the right function, or maybe to use brutal
Anton> memory addresses.... anyway something to avoid stepping into the code
Anton> 50000 times.
Anton> Any ideas?

You can try putting a breakpoint on the particular template
instantiation you care about.  I'm not completely sure this is what
you're asking, though.

Tom


  reply	other threads:[~2010-05-10 19:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-04 13:23 Anton MOUKHARSKI
2010-05-10 19:27 ` Tom Tromey [this message]
     [not found]   ` <4BE9232A.40904@cea.fr>
2010-05-11 18:59     ` Tom Tromey

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=m3hbmfblsf.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=anton.moukharski@cea.fr \
    --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