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] new set/show multiple-choice-auto-select command (take 3)
Date: Sun, 03 Feb 2008 20:40:00 -0000	[thread overview]
Message-ID: <20080203204000.GB21614@adacore.com> (raw)
In-Reply-To: <ufxw9vnlt.fsf@gnu.org>

> > The change since the last time is that the default had been changed
> > to "all".
> 
> Is this the current behavior, or are we changing the behavior here?

It's kind of both :). If you remember some work has been done recently
to handle breakpoints with multiple locations. For instance, breaking
on a constructor results in at least 2 locations for the same
breakpoint. In that case, the behavior was the equivalent of having
the new setting set to "all", so we're not changing anything here.

But when dealing with homonyms (for instance, breaking on overloaded
methods), the standard behavior was to ask the user to select the ones
he wanted to break on. This patch makes things more consistent by
changing the behavior. Now, the debugger will break on all matches
by default - but the old behavior can be of course restored using
"ask".

Similarly in Ada, we used to ask the user by default. But we decided
to change this because we think that breaking on all matches is what
the user wants most of the time, and also to make it consistent with
the other languages.

-- 
Joel


  reply	other threads:[~2008-02-03 20:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-03  4:38 Joel Brobecker
2008-02-03  4:48 ` Daniel Jacobowitz
2008-02-03  5:06   ` Joel Brobecker
2008-02-03 19:37     ` Eli Zaretskii
2008-02-03 19:36 ` Eli Zaretskii
2008-02-03 20:40   ` Joel Brobecker [this message]
2008-02-04  4:08     ` Eli Zaretskii
2008-02-04  5:40       ` 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=20080203204000.GB21614@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