From: Yao Qi <yao@codesourcery.com>
To: Matthew Gretton-Dann <matthew.gretton-dann@arm.com>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>,
"pedro@codesourcery.com" <pedro@codesourcery.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [patch] Skip kill-after-signal.exp if hw single-step is not supported
Date: Tue, 09 Aug 2011 15:50:00 -0000 [thread overview]
Message-ID: <4E41574E.4030702@codesourcery.com> (raw)
In-Reply-To: <4E415111.7020107@arm.com>
On 08/09/2011 11:24 PM, Matthew Gretton-Dann wrote:
> Would this be better if it followed the pattern of the
> skip_hw_breakpoint_tests and skip_hw_watchpoint_tests family of
> functions in gdb.exp?
>
> So I would rename the function to skip_hw_single_step_tests[1], and test
> for the existence of gdb,no_hardware_watchpoints in the board info.
>
Personally, I don't like the procs' name skip_* in lib/gdb.exp. IMO,
procs in lib/gdb.exp of this kind is to check a certain property in
current env, and return the result. Leave the test case itself to
determine whether to skip or run.
"single_step_to_signal_handler_p" is not equivalent to "hardware single
step", because some targets have hardware single step, but can't step
into signal handler.
The property interested here is "whether we can single step into a
signal handler", instead of "whether target has hardware single step".
I am not good at naming functions, so ideas on a better/clear name is
welcome.
--
Yao (é½å°§)
next prev parent reply other threads:[~2011-08-09 15:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 14:52 Yao Qi
2011-07-20 15:06 ` Jan Kratochvil
2011-07-20 15:12 ` Pedro Alves
2011-07-24 11:40 ` Mark Kettenis
2011-08-09 14:32 ` Yao Qi
2011-08-09 15:24 ` Matthew Gretton-Dann
2011-08-09 15:50 ` Yao Qi [this message]
2011-08-18 4:53 ` ping : " Yao Qi
2011-08-28 14:44 ` Yao Qi
2011-09-14 7:18 ` ping 3: " Yao Qi
2011-09-18 2:42 ` Joel Brobecker
2011-09-18 10:22 ` [committed]: " Yao Qi
2011-07-23 23:28 ` Mark Kettenis
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=4E41574E.4030702@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=matthew.gretton-dann@arm.com \
--cc=pedro@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