new-operator

I try to follow this article: http://flipcode.com/archives/How_To_Find_Memory_Leaks.shtml to overload my new and delete functions in order to track memory leaks. however - if I try to compile, I get a C2365: "operator new": redefinition; previous definition was a "function" in the file xdebug xdebug gets included in xlocale - however, i can't find where my project is including xlocale I'm using MFC for multithreading in my project. Can someone tell me how I can get my memory leak tracking to work? //edit: So this is my findMemoryLeak.h which i include in the end of stdafx.h #ifndef

My question is what happens to the object allocated with the new operator that is inside a function call. A specific example: I have a private vector pV which I want to send to a object/function outside of the class, foo->func(std::vector<int> *vec) . I first tried to write foo->func( new std::vector<int>(pV) ) but this resulted in a memory leak (when said function is called repeatedly inside a loop). When I specifically created a new object, called the function and then deleted that object, the whole thing worked, without the memory leak. Shouldn't the newly created object 'expire' and be

I have been trying to create an XML using the simplexml library (v2.6.2) http://simple.sourceforge.net/home.php The XML I want to create has to hold an enum value, which should be case-sensitive. Following is the POJO : package pojos; public enum MyEnum { NEW("new"), OLD("old"); private final String value; MyEnum(String v) { value = v; } public String value() { return value; } public static MyEnum fromValue(String v) { for (MyEnum c: MyEnum.values()) { if (c.value.equals(v)) { return c; } } throw new IllegalArgumentException(v); } } Following is the serializer code : import java.io.File;

How to overload new and delete operator for a dll . I have written overloaded operators as part of the dll , but client linking with this dll does not use overloaded new and delete Here is what the C++ standard has to say about this, in section 17.6.4.6/3: The program's definitions (of the new / delete operators) are used instead of the default versions supplied by the implementation. Such replacement occurs prior to program startup. The program's definitions shall not be specified as inline . No diagnostic is required. If you read that carefully, it exactly explains the trouble you are having

Possible Duplicates: When to use “new” and when not to, in C++? When should I use the new keyword in C++? It seems like I could program something without ever using the word new , and I would never have to worry about deleting anything either, so why should I ever call it? From what I understand, it's because I would run out of stack memory. Is this correct? I guess my main question is, when should I call new ? It's a matter of object lifetime: if you stack-allocate your objects, the objects destructors will be called when these objects go out of scope (say, at the end of the method). This

In "The C++ Programming Language" book Stroustrup says: "To deallocate space allocated by new , delete and delete[] must be able to determine the size of the object allocated. This implies that an object allocated using the standard implementation of new will occupy slightly more space than a static object. Typically, one word is used to hold the object’s size. That means every object allocated by new has its size located somewhere in the heap. Is the location known and if it is how can I access it? In actual fact, the typical implementation of the memory allocators store some other