Re: 'make check' does nothing?

[Phil Edwards <pedwards at disaster dot jaj dot com>]

On Mon, May 21, 2001 at 03:22:02PM +0100, Jason Merrill wrote:
> Oh, I've got it.  Phil: do a cvs update -d in libstdc++-v3 to get the
> new testsuite/libstdc++-v3.dg directory.

Ah-ha.  Could've sworn I'd added -d to my update'n'build script.

Okay, next silly dejagnu question:  does this code from dg.exp

    ## Set ulimits.
    ## This should normally be handled on a per-test basis through @xxx@-keywords.
    ## The following limit is expressed in kilobytes.  For history, have a
    ## look at http://gcc.gnu.org/ml/libstdc++/2000-10/msg00029.html
    set maximum-memory-usage 16384
    set shell-ulimit-command ulimit
    remote_exec host ${shell-ulimit-command} "-d ${maximum-memory-usage}"
    remote_exec host ${shell-ulimit-command} "-v ${maximum-memory-usage}"

    # Main loop.
    dg-runtest [lsort [glob -nocomplain $srcdir/*/*.cc]] \
            "" $DEFAULT_CXXFLAGS

really have an effect?  It looks like the two calls to ulimit are being
executed in two sub-shells, which won't affect the memory limits when the
test executables are run.

I ask only because, now that I finally have the DG-based testsuite running,
the tests which used to lock up the system due to things like "malloc
(all_of_it);" are once again locking up my system.


Phil

-- 
pedwards at disaster dot jaj dot com  |  pme at sources dot redhat dot com
devphil at several other less interesting addresses in various dot domains
The gods do not protect fools.  Fools are protected by more capable fools.