From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Re: GDB <MULTIPLE> breakpoints, source lines
Date: Sat, 14 Feb 2009 16:08:00 -0000 [thread overview]
Message-ID: <20090214160804.GA32155@caradoc.them.org> (raw)
In-Reply-To: <gn6610$r7d$1@ger.gmane.org>
On Sat, Feb 14, 2009 at 01:22:38PM +0300, Vladimir Prus wrote:
> > My question is: are there any circumstances in which you can get a
> > different source file or line for each location?
>
> There should be none, except that we had a bug report whereby GDB would
> create multiple location breakpoint where each location has the same
> line number and file basename, but different directories.
Do you think we'll ever use these for e.g. breakpoints on overloaded
functions?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-02-14 16:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-14 9:29 Peter Wainwright
2009-02-14 10:22 ` Vladimir Prus
2009-02-14 12:03 ` Peter Wainwright
2009-02-14 16:08 ` Daniel Jacobowitz [this message]
2009-02-14 16:39 ` Pierre Muller
2009-02-14 16:43 ` Vladimir Prus
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=20090214160804.GA32155@caradoc.them.org \
--to=drow@false.org \
--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