From: Andrew Cagney <cagney@gnu.org>
To: gdb-patches@sources.redhat.com
Subject: [rfa/testsuite] Extend signull to work with discriptors
Date: Wed, 16 Jun 2004 02:00:00 -0000 [thread overview]
Message-ID: <40CFA9B0.2050201@gnu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 213 bytes --]
Hello,
This patch extends signull (null pointer tests) so that:
- it really works with null descriptors (at least on ia64)
- checks both data read and write (at least on ia64 and ppc)
comments? michael?
Andrew
[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 2796 bytes --]
2004-06-15 Andrew Cagney <cagney@gnu.org>
* gdb.base/signull.c (bowler): Replace data_pointer with data_read
and data_write cases. Add code_descriptor case.
(zero, desc): New array and pointer.
(data, code): Change to simple pointers.
* gdb.base/signull.exp: Fix probe pattern matching a function
descriptor SIGSEGV. Replace data_pointer with data_read and
data_write tests.
Index: gdb.base/signull.c
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/signull.c,v
retrieving revision 1.3
diff -p -u -r1.3 signull.c
--- gdb.base/signull.c 22 May 2004 13:14:22 -0000 1.3
+++ gdb.base/signull.c 16 Jun 2004 01:55:19 -0000
@@ -22,7 +22,7 @@
#include <stdlib.h>
enum tests {
- code_entry_point, code_descriptor, data_pointer
+ code_entry_point, code_descriptor, data_read, data_write
};
static volatile enum tests test;
@@ -31,8 +31,10 @@ static volatile enum tests test;
typedef long data_t;
typedef long code_t (void);
-static volatile data_t *data[10];
-static volatile code_t *code[10];
+volatile data_t *data;
+volatile code_t *code;
+volatile data_t zero[10];
+volatile code_t *desc = (void *) zero;
sigjmp_buf env;
@@ -47,12 +49,14 @@ bowler (void)
{
switch (test)
{
- case data_pointer:
- return *data[0];
+ case data_read:
+ return (*data);
+ case data_write:
+ return (*data) = 1;
case code_entry_point:
- return code[0] ();
+ return (*code) ();
case code_descriptor:
- return ((code_t *) &code) ();
+ return (*desc) ();
}
}
Index: gdb.base/signull.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/signull.exp,v
retrieving revision 1.1
diff -p -u -r1.1 signull.exp
--- gdb.base/signull.exp 13 May 2004 18:12:07 -0000 1.1
+++ gdb.base/signull.exp 16 Jun 2004 01:55:19 -0000
@@ -79,7 +79,7 @@ gdb_test "set test = code_entry_point" "
set test "probe function pointer"
set function_pointer code_entry_point
gdb_test_multiple "continue" "$test" {
- -re "Program received signal SIGSEGV.* bowler .$gdb_prompt $" {
+ -re "Program received signal SIGSEGV.*bowler .*$gdb_prompt $" {
set function_pointer code_descriptor
pass "$test (function descriptor)"
}
@@ -109,7 +109,10 @@ proc test_segv { name tag bt_from_segv b
gdb_test backtrace $bt_from_keeper "backtrace keeper for ${name}"
}
-test_segv data data_pointer \
+test_segv data-read data_read \
+ {#0 .* bowler .*#1 .* main .*} \
+ {#0 .* keeper .*#1 .* handler .*#2 .* bowler .*#3 .* main .*}
+test_segv data-write data_write \
{#0 .* bowler .*#1 .* main .*} \
{#0 .* keeper .*#1 .* handler .*#2 .* bowler .*#3 .* main .*}
test_segv code $function_pointer \
next reply other threads:[~2004-06-16 2:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 2:00 Andrew Cagney [this message]
2004-06-16 5:02 Michael Elizabeth Chastain
2004-06-16 14:54 ` Andrew Cagney
2004-06-16 15:39 Michael Elizabeth Chastain
2004-06-16 16:43 ` 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=40CFA9B0.2050201@gnu.org \
--to=cagney@gnu.org \
--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