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

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

Re: Using setrlimit in testsuite

To: Phil Edwards <pedwards at disaster dot jaj dot com>
Subject: Re: Using setrlimit in testsuite
From: Zack Weinberg <zackw at panix dot com>
Date: Mon, 6 Aug 2001 15:29:28 -0400
Cc: Benjamin Kosnik <bkoz at redhat dot com>, libstdc++ at gcc dot gnu dot org
References: <20010805215230.A21876@disaster.jaj.com> <Pine.SOL.3.91.1010806093949.7174A-100000@taarna.cygnus.com> <20010806142248.A23676@disaster.jaj.com>

On Mon, Aug 06, 2001 at 02:22:48PM -0400, Phil Edwards wrote:
> On Mon, Aug 06, 2001 at 09:45:39AM -0700, Benjamin Kosnik wrote:
> > > Okay, I have an initial patch for this, and I've re-enabled the
> > > pathological test in insert.cc and ctor_copy_dtor.cc.  I'll wait to see
> > > what the autobuilder comes up with overnight before posting a full patch.
> 
> Crumbs.  The -static test fails to catch bad_alloc; the normal shared
> build is fine.  So my testsuite results go down by one.

How odd.  If you could put the static binary (unstripped, please)
somewhere I can download it, I can try to debug it.

zw

References:
- Using setrlimit in testsuite
  - From: Phil Edwards
- Re: Using setrlimit in testsuite
  - From: Benjamin Kosnik
- Re: Using setrlimit in testsuite
  - From: Phil Edwards

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