From: Stephane Carrez <stcarrez@nerim.fr>
To: gdb-patches@sources.redhat.com
Subject: [RFA]: Don't execute gdb.mi/mi-syn-frame.exp when gdb,nosignals
Date: Sun, 23 Feb 2003 20:48:00 -0000 [thread overview]
Message-ID: <3E59338E.8010109@nerim.fr> (raw)
[-- Attachment #1: Type: text/plain, Size: 381 bytes --]
Hi!
The test mi-syn-frame.exp uses signals (signal, alarm, sleep, SIGALRM) but signals
are not always available.
Can you approve this patch to test gdb,nosignals and avoid executing this test?
(see gdb.base/signals.exp which does the same)
Thanks,
Stephane
2003-02-23 Stephane Carrez <stcarrez@nerim.fr>
* mi-syn-frame.exp: Don't run this test when gdb,nosignals is set.
[-- Attachment #2: mi-syn-frame.exp.diffs --]
[-- Type: text/plain, Size: 910 bytes --]
Index: testsuite/gdb.mi/mi-syn-frame.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.mi/mi-syn-frame.exp,v
retrieving revision 1.1
diff -u -p -r1.1 mi-syn-frame.exp
--- testsuite/gdb.mi/mi-syn-frame.exp 2 Feb 2003 05:51:09 -0000 1.1
+++ testsuite/gdb.mi/mi-syn-frame.exp 23 Feb 2003 20:43:45 -0000
@@ -1,4 +1,4 @@
-# Copyright 2002 Free Software Foundation, Inc.
+# Copyright 2002, 2003 Free Software Foundation, Inc.
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
@@ -19,6 +19,11 @@
# Test MI output with synthetic frames on the stack (call dummies,
# signal handlers).
+
+if [target_info exists gdb,nosignals] {
+ verbose "Skipping mi-syn-frame.exp because of nosignals."
+ continue
+}
load_lib mi-support.exp
set MIFLAGS "-i=mi"
next reply other threads:[~2003-02-23 20:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-23 20:48 Stephane Carrez [this message]
2003-02-24 7:23 ` Andrew Cagney
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=3E59338E.8010109@nerim.fr \
--to=stcarrez@nerim.fr \
--cc=gdb-patches@sources.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