Re: Memory leask in STLPort
What makes you so sure that the problem does not lie with rArguments.DumpArgs()?
Re: Memory leask in STLPort
This rArguments::DumpArgs() simply print the arguments in to one text file. I am not allocating any memory for that.
Re: Memory leask in STLPort
Quote:
Originally Posted by suraani
This rArguments::DumpArgs() simply print the arguments in to one text file. I am not allocating any memory for that.
You probably are allocating memory, but perhaps not manually, and memory is not the only resource. Show the definition of the DumpArgs() member function, along with the relevant parts of the class definition.
1 Attachment(s)
Re: Memory leask in STLPort
Actually this function is defined in CTIOS libraries. Here I am attaching that header file. I am using this function only in one place.
Re: Memory leask in STLPort
Quote:
Originally Posted by suraani
Actually this function is defined in CTIOS libraries.
Right, so you are caught between a standard library implementation and a domain specific library. A quick search brings up STLport string 'leaking'. If the suggestion does not solve your problem then you might want to either switch to a different standard library implementation, or request for help from the STLport implementers.