Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Markus Deuling <deuling@de.ibm.com>
Cc: drow@false.org, gdb-patches@sourceware.org, uweigand@de.ibm.com
Subject: Re: [patch]: User choice for multiply-defined symbols
Date: Thu, 08 May 2008 16:33:00 -0000	[thread overview]
Message-ID: <u8wyldt85.fsf@gnu.org> (raw)
In-Reply-To: <48228023.3080503@de.ibm.com>

> Date: Thu, 08 May 2008 06:22:59 +0200
> From: Markus Deuling <deuling@de.ibm.com>
> 
> Daniel Jacobowitz schrieb:
> > GDB has done this for years and years.  I guess these are just normal
> > C symbols rather than C++ overloaded symbols, though, so that's the
> > difference?
> > 
> > I'm worried about all the different ways of dealing with lists of
> > symbols.  If we can already ask to set a breakpoint at foo(int) or
> > foo(int, int) why does this code have to be in a separate place?
> > 
> 
> It improves user experience. If there are symbols with the same name (it doesn't care about 
> the signature of a function) in different modules of your application you *can* now ask GDB to let you choose
> which of them to take. Normal operation would be to return the first symbol found.
> 
> Another advantage is, that the user is now able to choose one or more symbols from the list. For example:
> 
> (gdb) break foo
> [0] cancel
> [1] all
> [2] foo at ../../../../src/gdb/testsuite/gdb.base/multiple_symbols_mod.c:5
> [3] foo at ../../../../src/gdb/testsuite/gdb.base/multiple_symbols.c:14 
> [4] foo at ../../../../src/gdb/testsuite/gdb.base/multiple_symbols_two.c:42
> [5] foo at ../../../../src/gdb/testsuite/gdb.base/multiple_symbols_three.c:23
> 
> The user can choose for example symbol 3 and 5 for setting a breakpoint.

Like Daniel, I'm also confused.  Could someone please post a complete
list of GDB features related to setting breakpoints at several places
whose names are similar/identical, with a short summary of when each
one is useful?  I think we should consider all these features at once,
from the user perspective, and I don't see how can we reason about
usability without having a complete picture.

Thanks.


      reply	other threads:[~2008-05-08  9:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-05  8:36 Markus Deuling
2008-05-05  9:06 ` Vladimir Prus
2008-05-05 10:11   ` Markus Deuling
2008-05-05 12:58 ` Daniel Jacobowitz
2008-05-07 11:36   ` Markus Deuling
2008-05-07 22:00     ` Daniel Jacobowitz
2008-05-08 11:43       ` Markus Deuling
2008-05-08 16:33         ` Eli Zaretskii [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=u8wyldt85.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=deuling@de.ibm.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=uweigand@de.ibm.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