|
-
February 12th, 2010, 01:18 PM
#1
Memory allocation per static library
Hello,
Odd question today...
I am writing software that uses a static library for most of its runtime.
The library includes a memory debugger that uses overloaded new/delete and replacement malloc/free/calloc/recalloc/realloc for the debugger, declared and defined in the header (which is not used in the library) with definitions exposed in the source file.
My library also includes several other libraries as source, such as Lua. My headers in the library set it to use normal new/delete operators.
The problem seems to be that it's NOT using it's own operators, but is leaving them as undefined operators to be defined by the engine. Since the engine is getting the debugger operators, it attaches to them, and causes crashes as my library is supposed to use normal operators.
What can I do to fix this? Thanks!
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|