From: Pedro Alves <palves@redhat.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Support command "catch syscall" properly on different targets
Date: Tue, 03 Mar 2015 12:38:00 -0000 [thread overview]
Message-ID: <54F5AB4A.9080206@redhat.com> (raw)
In-Reply-To: <86pp8qi8ui.fsf@gmail.com>
On 03/03/2015 12:06 PM, Yao Qi wrote:
> Pedro Alves <palves@redhat.com> writes:
>
>> Do we actually need to do anything when the inferior is created?
>> Supposedly once the inferior is created, we'll try to insert
>> the catchpoint, and that will fail is the target does not
>> support it.
>
> No, but we need to tweak test case to emit UNSUPPORTED instead of FAIL
> if the target doesn't support "catch syscall".
Yeah, I'm imagining that we'll just detect it like we detect failures
to insert hardware breakpoints / watchpoints, at resume time.
Something like:
set test "continue with catch syscall"
gdb_test_multiple "continue" $test {
-re "Could not insert syscall catchpoint.*$gdb_prompt $" {
...
}
-re "Breakpoint .*$gdb_prompt $" {
...
}
}
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-03-03 12:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 14:23 Yao Qi
2015-02-27 18:49 ` Doug Evans
2015-03-03 11:56 ` Yao Qi
2015-03-03 12:14 ` Pedro Alves
2015-02-27 18:50 ` Pedro Alves
2015-03-03 12:06 ` Yao Qi
2015-03-03 12:38 ` Pedro Alves [this message]
2015-02-27 21:04 ` Sergio Durigan Junior
2015-03-03 12:11 ` Yao Qi
2015-03-03 12:29 ` Pedro Alves
2015-03-03 18:06 ` Sergio Durigan Junior
2015-03-03 18:18 ` Pedro Alves
2015-03-06 16:36 ` Yao Qi
2015-03-06 22:04 ` Sergio Durigan Junior
2015-03-09 14:29 ` Yao Qi
2015-03-10 4:53 ` Sergio Durigan Junior
2015-03-09 14:10 ` Yao Qi
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=54F5AB4A.9080206@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).