Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] unexpected multiple location for breakpoint
Date: Thu, 30 Dec 2010 21:03:00 -0000	[thread overview]
Message-ID: <E1PYGEM-0001sJ-Lz@fencepost.gnu.org> (raw)
In-Reply-To: <20101230080009.GJ2396@adacore.com> (message from Joel Brobecker	on Thu, 30 Dec 2010 12:00:09 +0400)

> Date: Thu, 30 Dec 2010 12:00:09 +0400
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org
> 
> I don't think we are worse, but the reason why I bring it up is because
> it's a definite departure from what we've been trying to do so far
> (minimize the number of breakpoint locations).

Maybe we have been doing that because multiple-location breakpoints
were not available until very recently?

> So, I'm just wondering if there might be some issues that I am not
> taking into consideration.
> 
> I'm willing to make that change, but this is going to require general
> consent among the maintainers

Right.  Would other maintainers please speak up on this issue?


  reply	other threads:[~2010-12-30 10:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-23  1:10 Joel Brobecker
2010-11-26 17:29 ` Joel Brobecker
2010-11-27 18:35   ` Daniel Jacobowitz
2010-12-10 12:23     ` Joel Brobecker
2010-12-28 11:50       ` Joel Brobecker
2010-12-28 20:15         ` Eli Zaretskii
2010-12-29  6:08           ` Joel Brobecker
2010-12-29  8:08             ` Joel Brobecker
2010-12-29 19:30             ` Eli Zaretskii
2010-12-30 20:40               ` Joel Brobecker
2010-12-30 21:03                 ` Eli Zaretskii [this message]
2010-12-31  6:35                 ` Michael Snyder

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=E1PYGEM-0001sJ-Lz@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.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