This is the mail archive of the libstdc++@sources.redhat.com 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: How to ... also libstdc++ bug report: memory leak at filebuf close on error.


On Mon, Sep 25, 2000 at 02:57:56PM -0400, George T. Talbot wrote:
> 
> I'll have to take a look at Socket++.  I didn't find it when I looked
> before, but I probably wasn't looking hard enough.  Bummer, because I'd
> rather not write such stuff myself.  ;^)

It hasn't been updated since 1997, and still uses pre-standard IOStreams,
etc.  Won't even compile on the platforms I have access to.  That's why
we're hoping to bring it up to date.  ("we" != "libstdc++-v3")


> This comes from line 80 of bits/std_fstream.h in the 2.90.3
> distribution.  Will this non-standard constructor remain in the shipping
> version?  (Please say yes...;^)

Ah, that one.  Sorry, I was lacking coffee previously.

Yeah, it's still in there, and I hope it stays there.  Currently that
second parameter for the name is unused.

This probably ought to go on the list of extensions.


> > Dunno about the memory leak problem.

What I should have said was, I honestly have no clue what's happening there.
:-)  I don't have a working compile+lib-v3 on any systems at the moment, but
I'll try and at least look at the runtime behavior of your code once I do.

Phil

-- 
pedwards at disaster dot jaj dot com  |  pme at sources dot redhat dot com
devphil at several other less interesting addresses in various dot domains
The gods do not protect fools.  Fools are protected by more capable fools.

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