From: Pedro Alves <palves@redhat.com>
To: Antoine Tremblay <antoine.tremblay@ericsson.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH v2] Fix breakpoint thread condition missing with mi and a pending breakpoint.
Date: Mon, 23 Mar 2015 19:52:00 -0000 [thread overview]
Message-ID: <55106F14.50102@redhat.com> (raw)
In-Reply-To: <1427124548-19126-1-git-send-email-antoine.tremblay@ericsson.com>
On 03/23/2015 03:29 PM, Antoine Tremblay wrote:
> In this patch v2:
> - comments are fixed as requested, sorry about that.
> - returns are on their own line.
> - Space before parens is fixed.
> - English errors in the test fixed.
> - mi_gdb_test "-break-delete 3" ".*" "" is now more specific :
> mi_gdb_test "-break-delete 3" "\\^done" "Delete breakpoint 3"
OK.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-03-23 19:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 19:06 [PATCH] " Antoine Tremblay
2015-03-05 13:10 ` Antoine Tremblay
2015-03-06 19:38 ` Pedro Alves
2015-03-23 15:29 ` [PATCH v2] " Antoine Tremblay
2015-03-23 19:52 ` Pedro Alves [this message]
2015-03-24 17:09 ` Pedro Alves
2015-03-24 17:32 ` [PATCH] Fix mi-pending.exp test output to allow stable test diffing Antoine Tremblay
2015-03-24 17:47 ` Pedro Alves
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=55106F14.50102@redhat.com \
--to=palves@redhat.com \
--cc=antoine.tremblay@ericsson.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