public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: edh@twcny.rr.com
To: gcc-gnats@gcc.gnu.org
Subject: libstdc++/6594: strstreambuf leaks 16 bytes - gcc 3.0.x
Date: Tue, 07 May 2002 07:56:00 -0000	[thread overview]
Message-ID: <20020507144741.12275.qmail@sources.redhat.com> (raw)


>Number:         6594
>Category:       libstdc++
>Synopsis:       strstreambuf leaks 16 bytes - gcc 3.0.x
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue May 07 07:56:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Ed Hourigan
>Release:        gcc 3.0.4
>Organization:
>Environment:
Red Hat Linux 7.2 on x86 processor
>Description:
The default constructor for strstreambuf allocates a
buffer of 16 bytes.  If you assign a user supplied
buffer by calling setp(...), then the 16 byte buffer is
not released and the pointer is lost.
I have verified this leak using the linux tool 'memprof'

Sample code:
( I am deriving a class from strstreambuf so I can control
  where the output stream goes )

class MyStreambuf : public strstreambuf 
{
public:

    MyStreambuf()
    {
       setp( _buffer, _buffer, _buffer+BUFSIZE );  // leak 
here!
    ...

    }

private:
    static const int BUFSIZE=256;
    char _buffer[BUFSIZE];
}
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-05-07 14:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-07  7:56 edh [this message]
2002-05-15  5:57 bkoz
2002-05-15 17:36 Ed Hourigan
2002-05-17  3:09 bkoz
2002-08-02 13:51 bkoz
2003-01-07 16:24 bkoz

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=20020507144741.12275.qmail@sources.redhat.com \
    --to=edh@twcny.rr.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).