This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

DejaGNU gurus ahoi! (Re: Testing use of STDIN redirected etc.)


Hi,

what would be the best way to test stuff like two binaries
communicating via a pipe, FIFO or such with DejaGNU? The gfortran
testsuite has by now quite extensive coverage of all the weird and
quirky corner cases of Fortran I/O behavior, but practically all these
tests are done using regular files. Over the years we've had some
embarrassing bugs in handling non-seekable files like terminals,
FIFO's, and pipes. I believe these would have been quickly caught if
only we had testing coverage.

(Something which works only on x86_64-unknown-linux-gnu and perhaps a
few other "mainstream" targets where we can expect the presence of a
"normal" shell environment etc., while not optimal, is certainly a lot
better than what we have now.)

Any ideas? See also the mail below which discusses the same issue.

On Mon, Oct 6, 2014 at 3:29 AM, Jerry DeLisle <jvdelisle@charter.net> wrote:
> Hi all,
>
> Over the years we have had a number of regressions related to reading from
> STDIN.
>
> Would it be acceptable to add a sub-directory such as
> gfortran.dg/testscripts.
>
> In this location we put one or more scripts to be executed to perform tests
> outside of the dejagnu environment.
>
> Within gfortran.dg we place a { dg-run } program that invokes the test
> scripts and checks the results.
>
> Is this doable? Anyone have any better ideas?
>
> Regards,
>
> Jerry



-- 
Janne Blomqvist


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]