Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Bogdan Slusarczyk <bodzio131@op.pl>
Cc: gdb-patches@sourceware.org, Vladimir Prus <vladimir@codesourcery.com>
Subject: Re: [PATCH, gdb6.8] -break-list doesn't list multiple breakpoints
Date: Mon, 14 Apr 2008 18:22:00 -0000	[thread overview]
Message-ID: <20080414175043.GA1968@caradoc.them.org> (raw)
In-Reply-To: <47F3946A.3090000@op.pl>

On Wed, Apr 02, 2008 at 04:12:58PM +0200, Bogdan Slusarczyk wrote:
> Hi everyone, I wrote my own patch for -break-list. I'm not sure that it  
> meets all requirements mentioned in  
> http://sourceware.org/ml/gdb-patches/2008-01/msg00251.html and previous  
> discussions, but combination -break-list + multiple breakpoints is now  
> usable for me. I'm not familiar with gdb test suit, so it's NOT tested at 
> all (except few my own cases).

There was some discussion of the behavior of multiple-location
breakpoints after this patch was posted, but no discussion of the
actual patch.  Volodya, could you look at it - does this seem like the
right way?

Bogdan, thanks for the patch.  Are you interested in further
contribution to GDB?  If so, I can send you the copyright paperwork we
require; I think this sneaks by just under the limit, but we prefer to
have it on file for the future.

To commit this we'll eventually need manual and testsuite updates.
You don't necessarily have to handle those yourself (though I'm sure
it would be appreciated if you did - on the other hand, at that point
we'd definitely need the paperwork).

-- 
Daniel Jacobowitz
CodeSourcery


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

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-02 17:16 Bogdan Slusarczyk
2008-04-03  5:42 ` Nick Roberts
2008-04-03  6:44   ` Vladimir Prus
2008-04-03  9:21     ` Nick Roberts
2008-04-03 10:00       ` Vladimir Prus
2008-04-03 10:45         ` Nick Roberts
2008-04-03 10:49           ` Vladimir Prus
2008-04-03 11:28             ` Nick Roberts
2008-04-03 11:39               ` Vladimir Prus
2008-04-03 11:52               ` Bogdan Slusarczyk
2008-04-03 12:12                 ` Vladimir Prus
2008-04-03 12:48                   ` Bogdan Slusarczyk
2008-04-14 18:22 ` Daniel Jacobowitz [this message]
2008-04-15  8:35   ` Vladimir Prus
2008-04-15 20:13   ` Bogdan Slusarczyk

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=20080414175043.GA1968@caradoc.them.org \
    --to=drow@false.org \
    --cc=bodzio131@op.pl \
    --cc=gdb-patches@sourceware.org \
    --cc=vladimir@codesourcery.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