public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bjornw@planetarion.com
To: gcc-gnats@gcc.gnu.org
Subject: libstdc++/4219: stl_alloc using -D__USE_MALLOC fails
Date: Tue, 04 Sep 2001 01:46:00 -0000 [thread overview]
Message-ID: <20010904084010.14630.qmail@sourceware.cygnus.com> (raw)
>Number: 4219
>Category: libstdc++
>Synopsis: stl_alloc using -D__USE_MALLOC fails
>Confidential: no
>Severity: critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Sep 04 01:46:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: bjornw@planetarion.com
>Release: gcc version 3.1 20010901 (experimental)
>Organization:
>Environment:
redhat-6.2 (all pacthed up june 2001), kernel-2.4.9
>Description:
I have a heavy multithreaded application (database server proxy with connection pooling) using stl and friends. Historically gcc-2 leaked memory while using builtin memory allocation scheme. Using -D__USE_MALLOC enforcing simple memory allocation classes was the only way to make my servers live for more than 5 minutes without eating up 500MB RAM.
g++ fails to compile anything cause a bug in stl_alloc.h
>How-To-Repeat:
Compile a program using -D__USE_MALLOC
>Fix:
stl_alloc.h: 258
Original code:
# ifdef __USE_MALLOC
typedef malloc_alloc alloc;# ifdef __USE_MALLOC
typedef malloc_alloc single_client_alloc;
#else
Change this into:
# ifdef __USE_MALLOC
typedef __mem_interface alloc;
typedef __mem_interface single_client_alloc;
# else
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2001-09-04 1:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-04 1:46 bjornw [this message]
2001-09-04 14:02 ljrittle
2001-11-03 15:49 ljrittle
2001-11-03 18:56 ljrittle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010904084010.14630.qmail@sourceware.cygnus.com \
--to=bjornw@planetarion.com \
--cc=gcc-gnats@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).