From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org
Cc: Daniel Jacobowitz <drow@false.org>
Subject: Re: [patch] fileio.exp FAILs if run as root
Date: Wed, 12 Dec 2007 16:26:00 -0000 [thread overview]
Message-ID: <20071211183846.GA15795@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <20071211175423.GA8014@caradoc.them.org>
[-- Attachment #1: Type: text/plain, Size: 232 bytes --]
On Tue, 11 Dec 2007 18:54:23 +0100, Daniel Jacobowitz wrote:
...
> I think a warning is quite sufficient. Perhaps in the FAIL message.
Attached.
Still there is an XFAIL for Cygwin so it IMO could be even for UNIX.
Regards,
Jan
[-- Attachment #2: gdb-cvs-test-fileio-root-run2.patch --]
[-- Type: text/plain, Size: 1358 bytes --]
2007-12-11 Jan Kratochvil <jan.kratochvil@redhat.com>
* gdb.base/fileio.exp: Add the testcase purpose comment at the top.
Embed a warning into the name of two testcases known to fail if we run
as root.
--- ./gdb/testsuite/gdb.base/fileio.exp 23 Aug 2007 18:14:16 -0000 1.12
+++ ./gdb/testsuite/gdb.base/fileio.exp 11 Dec 2007 18:22:44 -0000
@@ -17,6 +17,8 @@
# bug-gdb@prep.ai.mit.edu
# This file was written by Corinna Vinschen <vinschen@redhat.com>
+# Its main purpose is to test the GDB implementation of the remote file I/O
+# protocol.
if [target_info exists gdb,nofileio] {
verbose "Skipping fileio.exp because of no fileio capabilities."
@@ -92,7 +94,7 @@ catch "system \"chmod -f -w nowrt.fileio
gdb_test continue \
"Continuing\\..*open 5:.*EACCES$stop_msg" \
-"Open for write but no write permission returns EACCES"
+"Open for write but no write permission returns EACCES (it also fails if running as root)"
gdb_test continue \
"Continuing\\..*write 1:.*OK$stop_msg" \
@@ -234,7 +236,7 @@ if [ishost *cygwin*] {
}
gdb_test continue \
"Continuing\\..*unlink 2:.*EACCES$stop_msg" \
-"Unlinking a file in a directory w/o write access returns EACCES"
+"Unlinking a file in a directory w/o write access returns EACCES (it also fails if running as root)"
gdb_test continue \
"Continuing\\..*unlink 3:.*ENOENT$stop_msg" \
prev parent reply other threads:[~2007-12-11 18:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-08 18:58 Jan Kratochvil
2007-12-08 19:13 ` Mark Kettenis
2007-12-09 1:19 ` Jan Kratochvil
2007-12-11 17:46 ` Michael Snyder
2007-12-11 17:54 ` Jan Kratochvil
2007-12-11 18:38 ` Daniel Jacobowitz
2007-12-12 16:26 ` Jan Kratochvil [this message]
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=20071211183846.GA15795@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=drow@false.org \
--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