From: Andrew Cagney <ac131313@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: [patch/rfc] KFAIL EBUSY kernel bug
Date: Thu, 08 Jan 2004 20:12:00 -0000 [thread overview]
Message-ID: <3FFDB9A7.4090801@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 211 bytes --]
Hello,
Ref: http://sources.redhat.com/gdb/bugs/1502
Turns out that the EBUSY error status value I was seeing is a Linux
Kernel bug. This KFAIL's that case.
baring problems, I'll commit in a few days
Andrew
[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 1327 bytes --]
2004-01-08 Andrew Cagney <cagney@redhat.com>
* gdb.base/fileio.exp: For "Renaming a directory to a non-empty
directory returns ENOTEMPTY or EEXIST", treat EBUSY as a KFAIL.
Index: gdb.base/fileio.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/fileio.exp,v
retrieving revision 1.5
diff -u -r1.5 fileio.exp
--- gdb.base/fileio.exp 10 Nov 2003 09:12:20 -0000 1.5
+++ gdb.base/fileio.exp 8 Jan 2004 20:09:20 -0000
@@ -216,9 +216,16 @@
"Renaming a file to existing directory returns EISDIR"
send_gdb "tbreak 388\n" ; gdb_expect -re "$gdb_prompt $"
-gdb_test continue \
- "Continuing\\..*rename 3:.*(ENOTEMPTY|EEXIST).*test_rename \\(\\) at.*$srcfile:388.*" \
-"Renaming a directory to a non-empty directory returns ENOTEMPTY or EEXIST"
+set test "Renaming a directory to a non-empty directory returns ENOTEMPTY or EEXIST"
+gdb_test_multiple continue "${test}" {
+ -re "Continuing\\..*rename 3:.*(ENOTEMPTY|EEXIST).*test_rename \\(\\) at.*$srcfile:388.*" {
+ pass "${test}"
+ }
+ -re "Continuing\\..*rename 3:.*EBUSY.*test_rename \\(\\) at.*$srcfile:388.*" {
+ # On NFS, GNU/Linux <= 2.6/2004-01-08 at least, gets this wrong
+ kfail gdb/1502 "${test}"
+ }
+}
send_gdb "tbreak 393\n" ; gdb_expect -re "$gdb_prompt $"
gdb_test continue \
next reply other threads:[~2004-01-08 20:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-08 20:12 Andrew Cagney [this message]
2004-01-08 20:20 ` Daniel Jacobowitz
2004-01-08 20:33 ` Andrew Cagney
2004-01-12 14:46 ` Andrew Cagney
2004-01-08 20:58 Michael Elizabeth Chastain
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=3FFDB9A7.4090801@redhat.com \
--to=ac131313@redhat.com \
--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