From: Vladimir Prus <vladimir@codesourcery.com>
To: Bogdan Slusarczyk <bodzio131@op.pl>, gdb-patches@sourceware.org
Subject: Re: [PATCH, gdb6.8] -break-list doesn't list multiple breakpoints
Date: Tue, 15 Apr 2008 08:35:00 -0000 [thread overview]
Message-ID: <200804151213.29064.vladimir@codesourcery.com> (raw)
In-Reply-To: <20080414175043.GA1968@caradoc.them.org>
On Monday 14 April 2008 21:50:43 Daniel Jacobowitz wrote:
> 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?
I'll review this patch, but I think only when I get back from the
KDevelop hackathon -- so not earlier than this Saturday.
- Volodya
next prev parent reply other threads:[~2008-04-15 8:14 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
2008-04-15 8:35 ` Vladimir Prus [this message]
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=200804151213.29064.vladimir@codesourcery.com \
--to=vladimir@codesourcery.com \
--cc=bodzio131@op.pl \
--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