[ Home  |  FAQ-Related Q&As  |  General Q&As  |  Answered Questions ]

    Search the Q&A Archives

I saw a memory leak in fstream open call on IBM AIX. There...

<< Back to: comp.unix.aix Frequently Asked Questions (Part 5 of 5)

Question by Abhay Khoje
Submitted on 9/26/2006
Related FAQ: comp.unix.aix Frequently Asked Questions (Part 5 of 5)
Rating: Not yet rated Rate this question: Vote
I saw a memory leak in fstream open call on IBM AIX.
There is 33 bytes leak in fstream open call.

Snnippet of purify output:

MLK: 33 bytes leaked at 0x2018b238
  * This memory was allocated from:
malloc         [librtlib.o]
operator new(unsigned long) [libC.a(ansicore_32.o)]
operator new(unsigned long) [librtlib.o]
char* std::_Allocate<char>(unsigned long,char*) [libC.a(ansi_32.o)]
std::allocator<char>::allocate(unsigned long,const void*) [libC.a(ansi_32.o)]
std::basic_string<char,std::char_traits<char>,std::allocator<char> >::_Copy(unsigned long) [libC.a(ansi_32.o)]

I found this leak corresponds to the following line of code.

m_fsFile.open(m_strName.c_str(), nMode);

I have written a small test program that opens a file and purified it.

    char *m_strName = "/tmp/abhynew1";
    m_fsFile.open(m_strName, fstream::in | fstream::out | fstream::app);
    m_fsFile.close();

Purify shows a leak inside fstream. (Same output as shown above).

I did the same thing on Solaris, it shows no memory leak.

Could any body tell me that, is this the known problem? If yes, It would be great if some one pointes me to the correct AIX version which has fix for this.

Thanks in advance!

Regards,
Abhay Khoje


Your answer will be published for anyone to see and rate.  Your answer will not be displayed immediately.  If you'd like to get expert points and benefit from positive ratings, please create a new account or login into an existing account below.


Your name or nickname:
If you'd like to create a new account or access your existing account, put in your password here:
Your answer:

FAQS.ORG reserves the right to edit your answer as to improve its clarity.  By submitting your answer you authorize FAQS.ORG to publish your answer on the WWW without any restrictions. You agree to hold harmless and indemnify FAQS.ORG against any claims, costs, or damages resulting from publishing your answer.

 

FAQS.ORG makes no guarantees as to the accuracy of the posts. Each post is the personal opinion of the poster. These posts are not intended to substitute for medical, tax, legal, investment, accounting, or other professional advice. FAQS.ORG does not endorse any opinion or any product or service mentioned mentioned in these posts.

 

<< Back to: comp.unix.aix Frequently Asked Questions (Part 5 of 5)

[ Home  |  FAQ-Related Q&As  |  General Q&As  |  Answered Questions ]
© 2008 FAQS.ORG. All rights reserved.