This is the mail archive of the
mailing list for the GCC project.
Re: egcs-980321 on sparc-sun-solaris2.5.1 test results
- To: Horst von Brand <vonbrand at inf dot utfsm dot cl>
- Subject: Re: egcs-980321 on sparc-sun-solaris2.5.1 test results
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Sat, 28 Mar 1998 12:58:55 -0700
- cc: Robert Lipe <robertl at dgii dot com>, egcs at cygnus dot com
- Reply-To: law at cygnus dot com
In message <199803260454.AAA06627@pincoya.inf.utfsm.cl>you write:
> > Run the programs under a shell that supports limit control. Under
> > Solaris, I think this means ksh. Then use the shell's internal ulimit
> > to cap the max CPU time or stack or vm or anything else you need to
> > catch.
> That's something dejagnu would have to do for each compilation/execution.
> And if that is done, it's worth doing well, i.e., portably once and for
> all. Not being at all familiar with expect and dejagnu, I can't even start
> thinking about how to do it, but I'd expect expect to have the means for
> doing exactly that on its own. Maybe it is in there, and needs to be
> activated with some switch?
Dejagnu does have the concept of "timeouts", and I think if you wait
long enough they will kick in :-)
No, I don't know what the default value is -- I just know that some
of the longer running tests actually do time out when running on
a simulator. It may be the case that only the simulator testing
harness uses them. I don't really know.