Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Paul Hilfinger <hilfingr@gnat.com>
Cc: gdb@sourceware.org
Subject: Re: [RFC] multiple breakpoints from FILE:LINE
Date: Fri, 13 Jan 2006 15:23:00 -0000	[thread overview]
Message-ID: <20060113152350.GA9758@nevyn.them.org> (raw)
In-Reply-To: <20060113104212.0B28848CBD8@nile.gnat.com>

I'll read the rest of the replies momentarily but...

On Fri, Jan 13, 2006 at 05:42:12AM -0500, Paul Hilfinger wrote:
> 
> In response to
> 
>    break FUNCTION
> 
> in C++, GDB currently presents one with a list of choices when FUNCTION
> is overloaded.  However, this is not the only case in which the target 
> of a 'break' command is ambiguous.  Consider
> 
>    break FILENAME:LINENUM
> 
> Normally, this refers to a single location in a program, but if this line
> is in the middle of a C++ template, a multiply #included file, or an
> Ada generic definition, it may refer to several locations.  Currently,
> GDB chooses one of these silently.

We have discussed this issue many times in the past, as recently as two
weeks ago.  In the beginning of 2005 I posted a prototype patch to set
only a single breakpoint, but associate it with multiple locations.  I
still firmly believe that that is the correct solution.  However, the
patch was never finished.

Those menus have got to go.  They're (a) confusing to users (in my
opinion, no real data), and (b) extremely awkward for graphical
frontends.

-- 
Daniel Jacobowitz
CodeSourcery


  parent reply	other threads:[~2006-01-13 15:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-13 10:42 Paul Hilfinger
2006-01-13 11:32 ` Eli Zaretskii
2006-01-13 11:56   ` Joel Brobecker
2006-01-13 13:05     ` Eli Zaretskii
2006-01-13 14:17       ` Andrew STUBBS
2006-01-13 15:27         ` Daniel Jacobowitz
2006-01-13 15:25   ` Daniel Jacobowitz
2006-01-13 15:19 ` Paul Koning
2006-01-13 15:23 ` Daniel Jacobowitz [this message]
2006-01-13 15:40   ` Joel Brobecker
2006-01-14 10:15   ` Paul Hilfinger
2006-01-14 16:16     ` Daniel Jacobowitz
2006-01-15  1:51 : " Cyrille Comar
2006-01-15 22:23 ` Paul Hilfinger
2006-01-15 17:38 David Anderson
2006-01-15 17:50 ` Daniel Jacobowitz
2006-01-15 17:54 ` Robert Dewar
2006-01-15 18:33   ` Andreas Schwab
2006-01-15 19:06     ` Robert Dewar

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=20060113152350.GA9758@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=hilfingr@gnat.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