public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Carlo Wood <carlo@alinoe.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/5492: basic_string allocator problem
Date: Fri, 25 Jan 2002 15:46:00 -0000	[thread overview]
Message-ID: <20020125234603.15031.qmail@sources.redhat.com> (raw)

The following reply was made to PR libstdc++/5492; it has been noted by GNATS.

From: Carlo Wood <carlo@alinoe.com>
To: kk71878@hotmail.com
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: libstdc++/5492: basic_string allocator problem
Date: Sat, 26 Jan 2002 00:38:09 +0100

 On Fri, Jan 25, 2002 at 11:46:37AM -0600, kk71878@hotmail.com wrote:
 > with gcc 3.0.3, but when the program is stopped and re-started (re-loading the
 > data from the storage file, I get a valid basic_string object, but the data
 > within it is not valid.
 
 This sounds like a bug in the persistent object library,
 what makes you think it is a bug in libstdc++?
 
 >                                            (my inclination is that
 > basic_string's data is being allocated by the default allocator regardless
 > of any allocator passed as a template parameter)
 
 I have written a string class that replaces the allocator
 and it works for me.  You can see what I did by checking out
 module libcwd from cvs and looking at the file private_allocator.h
 and private_internal_string.h.
 
 My first thought is that you have forgotten to define
 a rebind<> member template.
 
 For info on how to obtain libcwd from cvs, see
 http://libcw.sourceforge.net/debugging/
 
 Regards,
 
 -- 
 Carlo Wood <carlo@alinoe.com>


             reply	other threads:[~2002-01-25 23:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-25 15:46 Carlo Wood [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-25  9:56 kk71878

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=20020125234603.15031.qmail@sources.redhat.com \
    --to=carlo@alinoe.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).