From: Andrew Cagney <cagney@gnu.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: Michael Elizabeth Chastain <mec.gnu@mindspring.com>,
drow@false.org, ac131313@redhat.com,
gdb-patches@sources.redhat.com
Subject: Re: [rfa] New test sigbpt.{c,exp}
Date: Wed, 07 Jul 2004 17:31:00 -0000 [thread overview]
Message-ID: <40EC3344.8050001@gnu.org> (raw)
In-Reply-To: <40EAFD7B.9020506@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 574 bytes --]
>> mec> How about:
>> mec> mec> (1) before running the program, 'disassemble bowler'
>> mec> (2) at the breakpoint, 'x/i $pc'
>> mec> check that the output of (2) matches one of the lines in (1)
>
>
> FYI, that's effectively what I did. It checks the $pc address against a table of valid instruction addresses. It doesn't match it fails, via gdb_test_multiple internals. All thats missing is a pattern to match any other pc address in bowler.
I've added the attached.
Andrew
> Trying to single-step after corrupting the $pc would be meaningless.
>
> Andrew
[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 728 bytes --]
2004-07-07 Andrew Cagney <cagney@gnu.org>
* gdb.base/sigbpt.exp (stepi_out): Check for a single step
corrupting the PC.
Index: gdb.base/sigbpt.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/sigbpt.exp,v
retrieving revision 1.1
diff -p -u -r1.1 sigbpt.exp
--- gdb.base/sigbpt.exp 6 Jul 2004 15:08:54 -0000 1.1
+++ gdb.base/sigbpt.exp 7 Jul 2004 17:28:50 -0000
@@ -184,6 +184,9 @@ proc stepi_out { name args } {
-re "pc *[after_segv] .*bowler.*$gdb_prompt $" {
kfail gdb/1702 "$test (skipped fault insn)"
}
+ -re "pc *0x\[a-z0-9\]* .*bowler.*$gdb_prompt $" {
+ kfail gdb/1702 "$test (corrupt pc)"
+ }
}
# Clear any breakpoints
next prev parent reply other threads:[~2004-07-07 17:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-06 18:59 Michael Elizabeth Chastain
2004-07-06 19:29 ` Andrew Cagney
2004-07-07 17:31 ` Andrew Cagney [this message]
2004-07-08 14:28 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2004-07-07 18:39 Michael Elizabeth Chastain
2004-07-06 18:12 Michael Elizabeth Chastain
2004-07-06 18:30 ` Daniel Jacobowitz
2004-06-30 18:53 Michael Elizabeth Chastain
2004-07-06 15:10 ` Andrew Cagney
2004-07-06 15:35 ` Daniel Jacobowitz
2004-07-06 16:00 ` Andrew Cagney
2004-06-30 3:53 Michael Elizabeth Chastain
2004-06-30 15:25 ` Andrew Cagney
2004-06-30 15:30 ` Daniel Jacobowitz
2004-07-02 13:24 ` Andrew Cagney
2004-06-29 23:44 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=40EC3344.8050001@gnu.org \
--to=cagney@gnu.org \
--cc=ac131313@redhat.com \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=mec.gnu@mindspring.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