From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] KFAIL EBUSY kernel bug
Date: Thu, 08 Jan 2004 20:33:00 -0000 [thread overview]
Message-ID: <3FFDBE80.2090603@redhat.com> (raw)
In-Reply-To: <20040108202006.GA13474@nevyn.them.org>
> On Thu, Jan 08, 2004 at 03:12:23PM -0500, Andrew Cagney wrote:
>
>> 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
>
>
> If it's a Linux kernel bug, that makes it an XFAIL, not a KFAIL.
Oops, yes (I had my Red Hat kernel, rather than FSF GDB glasses on).
>> 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.
>
>
> -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-01-08 20:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-08 20:12 Andrew Cagney
2004-01-08 20:20 ` Daniel Jacobowitz
2004-01-08 20:33 ` Andrew Cagney [this message]
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=3FFDBE80.2090603@redhat.com \
--to=ac131313@redhat.com \
--cc=drow@mvista.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