Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yufeng Zhang <Yufeng.Zhang@arm.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: [patch] Skip gdb.base/kill-after-signal.exp if gdb, nosignals
Date: Thu, 13 Dec 2012 19:20:00 -0000	[thread overview]
Message-ID: <50CA2A73.9020100@arm.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 451 bytes --]

Hi,

This patch adds check to gdb.base/kill-after-signal.exp to skip the test 
if the board has no support for signals, which is the case in most 
baremetal environment.  This patch follows the existing practice as what 
had been done to gdb.base/signull.exp,sigbpt.exp,etc.

Is it OK?

Thanks,
Yufeng


testsuite/

2012-12-13  Yufeng Zhang  <yufeng.zhang@arm.com>

         * gdb.base/kill-after-signal.exp: Disable if gdb,nosignals.

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: test-add-nosignals-check.patch --]
[-- Type: text/x-patch; name=test-add-nosignals-check.patch, Size: 535 bytes --]

diff --git a/gdb/testsuite/gdb.base/kill-after-signal.exp b/gdb/testsuite/gdb.base/kill-after-signal.exp
index 7b70510..91eec2d 100644
--- a/gdb/testsuite/gdb.base/kill-after-signal.exp
+++ b/gdb/testsuite/gdb.base/kill-after-signal.exp
@@ -20,6 +20,11 @@ if { ![can_single_step_to_signal_handler] } {
     return
 }
 
+if [target_info exists gdb,nosignals] {
+    verbose "Skipping kill-after-signal.exp because of nosignals."
+    continue
+}
+
 if [prepare_for_testing ${testfile}.exp ${testfile}] {
     return -1
 }

             reply	other threads:[~2012-12-13 19:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-13 19:20 Yufeng Zhang [this message]
2012-12-13 19:53 ` Pedro Alves
2012-12-14 11:03   ` Yufeng Zhang
2012-12-14 11:25     ` Pedro Alves
2012-12-14 13:39     ` 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=50CA2A73.9020100@arm.com \
    --to=yufeng.zhang@arm.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