This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: PR6678?
- From: Stefan Olsson <stefan at noname4us dot com>
- To: Paolo Carlini <pcarlini at unitus dot it>
- Cc: bkoz <bkoz at redhat dot com>, libstdc++ at gcc dot gnu dot org
- Date: Mon, 27 May 2002 14:36:04 +0200
- Subject: Re: PR6678?
- Organization: Noname4us
- References: <3CF22634.8000806@unitus.it>
Strange...
...we see the problem on all machines, for instance:
- Linux third 2.4.12 #1 SMP Mon Dec 17 23:41:57 CET 2001 i686 unknown
using glibc 2.2.3 with GCC 3.0.4 (libstdc++ 3.0.96)
- Linux snon 2.4.18 #29 Thu May 9 15:00:41 CEST 2002 i686 unknown using
glibc 2.2.5 with GCC 2.95.3
It seems like the bug or whatever it is has been around for quite a while...
Brgds
/Stefan
Paolo Carlini wrote:
> Hum...
>
> In fact, I have just tried both the testcases included in c++/6678 and
> could *not* reproduce the problem on my PII, linux2.4.16, glibc2.2.5
> system...
>
> This is what 'top' stabilizes to for the first one:
>
> PID USER PRI NI SIZE RSS SHARE STAT LIB %CPU %MEM TIME COMMAND
> 1120 paolo 15 0 796 796 692 R 0 96.6 0.3 0:08 a.out
>
> and this for the second one:
>
> PID USER PRI NI SIZE RSS SHARE STAT LIB %CPU %MEM TIME COMMAND
> 1127 paolo 19 0 796 796 692 R 0 96.9 0.3 0:18 a.out
>
> Benjamin, are you actually able to see the memory grow when running
> those two testcases??
>
> Ciao, Paolo.
>
>
>
>
>
--
In any organization there will always be one person who knows what is going on.
This person must be fired.