Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Markus Deuling <deuling@de.ibm.com>, gdb-patches@sourceware.org
Subject: Re: [RFA] new set/show multiple-choice-auto-select commands (take 2)
Date: Thu, 17 Jan 2008 14:51:00 -0000	[thread overview]
Message-ID: <20080117145052.GF28020@adacore.com> (raw)
In-Reply-To: <20080117142615.GA8662@caradoc.them.org>

> Why shouldn't GDB default to setting both breakpoints... like we do
> for template functions now?

That's the part I didn't understand. But since this was agreed on
earlier, I accepted it.

Note that, in Ada, we have made a different choice for the default
behavior: Instead of breaking everywhere by default, we ask the user
by default. This is something we have been doing at least since I joined
AdaCore 7 years ago, so I'd be reluctant to change the default, as it
might surprise Ada users using the FSF debugger. I am not strongly
opposed to the change, but I know I am going to have a very very hard
time convincing AdaCore of this change of behavior and we will likely
end up with different behaviors between the FSF GDB and AdaCore's.
Not that big a deal, but might be disruptive to Ada users who use both
(I know we have some customers who also use Ada at home and thus use
both).

> I am concerned that we now have too many different places where we
> have multiple symbols and breakpoints and we're handling them all
> differently.

I agree. I know that I submitted a patch that does not improve this
situation (addition of ada_finish_decode_line_1 I think), but I am very
motivated in making it better. This is really one of my major goals
for 2008. I will do that gradually, but in the meantime, I thought
that it would still be helpful addition to the FSF tree, as it provides
a feature that is critical in Ada, IMO.

I hope you don't object to the addition of this new set/show setting
whose purpose, I believe, is really orthogonal to the issue that
Markus is trying to address.

-- 
Joel


  reply	other threads:[~2008-01-17 14:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-16 13:56 Joel Brobecker
2008-01-17  6:37 ` Markus Deuling
2008-01-17 10:27   ` Joel Brobecker
2008-01-17 11:41     ` Markus Deuling
2008-01-17 12:31       ` Joel Brobecker
2008-01-17 14:26       ` Daniel Jacobowitz
2008-01-17 14:51         ` Joel Brobecker [this message]
2008-01-17 15:07           ` Daniel Jacobowitz
2008-01-23 15:33             ` 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=20080117145052.GF28020@adacore.com \
    --to=brobecker@adacore.com \
    --cc=deuling@de.ibm.com \
    --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