From: Pedro Alves <palves@redhat.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: gdb-patches@sourceware.org, Gabriel Krisman Bertazi <gabriel@krisman.be>
Subject: Re: [PATCH] Fix for PR breakpoints/16297: Fix catch syscall to work with syscall 0
Date: Mon, 16 Dec 2013 18:35:00 -0000 [thread overview]
Message-ID: <52AF47D5.1040304@redhat.com> (raw)
In-Reply-To: <m338lszn95.fsf@redhat.com>
On 12/16/2013 06:03 PM, Sergio Durigan Junior wrote:
> If it is OK to you, I will wait until my other patch
> touching catch-syscall.exp is approved, so that I can write a simple
> extension to the testcase that will test this specific bug. Then, I can
> commit both patches (this one and the testcase one) together.
Yes, sounds great.
Thanks,
--
Pedro Alves
next prev parent reply other threads:[~2013-12-16 18:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-15 3:58 Gabriel Krisman Bertazi
2013-12-15 4:04 ` Sergio Durigan Junior
2013-12-16 17:51 ` Pedro Alves
2013-12-16 17:57 ` Pedro Alves
2013-12-16 18:03 ` Sergio Durigan Junior
2013-12-16 18:35 ` Pedro Alves [this message]
2013-12-19 3:50 ` Sergio Durigan Junior
2013-12-19 16:21 ` Pedro Alves
2013-12-19 19:09 ` Sergio Durigan Junior
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=52AF47D5.1040304@redhat.com \
--to=palves@redhat.com \
--cc=gabriel@krisman.be \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@redhat.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