Re: failures in fileio.exp

[Andrew Cagney <ac131313@redhat.com>]

> On Wed, Jun 11, 2003 at 03:30:14PM -0700, David Carlton wrote:
> 
>> I'm seeing these failures in fileio.exp:
>> 
>> FAIL: gdb.base/fileio.exp: Stat a NULL pathname returns ENOENT
>> FAIL: gdb.base/fileio.exp: System with invalid command returns 127
>> FAIL: gdb.base/fileio.exp: Renaming a nonexistant file returns ENOENT
>> FAIL: gdb.base/fileio.exp: Unlinking a nonexistant file returns ENOENT
>> FAIL: gdb.base/fileio.exp: Time(2) returns feasible values
>> 
>> This is on Red Hat 8.0 (i686-pc-linux-gnu), GCC 3.1.  I'll include the
>> gdb.log below, if it helps.
> 
> 
> Fileio.exp only works for remote targets and then only for targets on
> which the fileio protocol is implemented.  I've added a conditional
> which only runs the test on remote targets.

My understanding from the thread discussing fileio.exp:
http://sources.redhat.com/ml/gdb-patches/2003-06/msg00410.html
was that it should work native.  Restricting it to the remote case would 
leave it open to bit rot.

The above indicate that this is true.  The differences are minor syscall 
nuances and can be handled with a bit of testsuite tweaking.

Andrew