Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/doco] Document "set/show multiple-symbols" command
Date: Fri, 04 Apr 2008 00:39:00 -0000	[thread overview]
Message-ID: <20080403215907.GB23283@adacore.com> (raw)
In-Reply-To: <ur6dokm28.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 336 bytes --]

> Other then that, this text is fine with me.

Thanks, Eli. I incorporated your suggestions and checked the patch in.
It occured to me that I should have proposed a NEWS entry as well:

2008-04-03  Joel Brobecker  <brobecker@adacore.com>

        * NEWS: Mention new commands set/show multiple-symbols.

OK to commit?

Thanks,
-- 
Joel

[-- Attachment #2: NEWS.diff --]
[-- Type: text/plain, Size: 686 bytes --]

Index: NEWS
===================================================================
RCS file: /cvs/src/src/gdb/NEWS,v
retrieving revision 1.263
diff -u -p -r1.263 NEWS
--- NEWS	14 Mar 2008 22:30:07 -0000	1.263
+++ NEWS	3 Apr 2008 21:56:55 -0000
@@ -25,6 +25,12 @@ show exec-wrapper
 unset exec-wrapper
   Use a wrapper program to launch programs for debugging.
 
+set multiple-symbols (all|ask|cancel)
+show multiple-symbols
+  The value of this variable can be changed to adjust the debugger behavior
+  when an expression or a breakpoint location contains an ambiguous symbol
+  name (an overloaded function name, for instance).
+  
 *** Changes in GDB 6.8
 
 * New native configurations

  parent reply	other threads:[~2008-04-03 21:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-02 21:02 Joel Brobecker
     [not found] ` <ur6dokm28.fsf@gnu.org>
2008-04-04  0:39   ` Joel Brobecker [this message]
2008-04-04  9:27     ` Eli Zaretskii
2008-04-04 17:22       ` Joel Brobecker

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=20080403215907.GB23283@adacore.com \
    --to=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@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