1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
|
/* +------------------------------------+
* | Inspire Internet Relay Chat Daemon |
* +------------------------------------+
*
* InspIRCd: (C) 2002-2009 InspIRCd Development Team
* See: http://wiki.inspircd.org/Credits
*
* This program is free but copyrighted software; see
* the file COPYING for details.
*
* ---------------------------------------------------
*/
#include "inspircd_win32wrapper.h"
#include <exception>
#include <new>
#include <new.h>
/** On windows, all dll files and executables have their own private heap,
* whereas on POSIX systems, shared objects loaded into an executable share
* the executable's heap. This means that if we pass an arbitrary pointer to
* a windows DLL which is not allocated in that dll, without some form of
* marshalling, we get a page fault. To fix this, these overrided operators
* new and delete use the windows HeapAlloc and HeapFree functions to claim
* memory from the windows global heap. This makes windows 'act like' POSIX
* when it comes to memory usage between dlls and exes.
*/
void * ::operator new(size_t iSize)
{
void* ptr = HeapAlloc(GetProcessHeap(), 0, iSize); /* zero memory for unix compatibility */
/* This is the correct behaviour according to C++ standards for out of memory,
* not returning null -- Brain
*/
if (!ptr)
throw std::bad_alloc();
else
return ptr;
}
void ::operator delete(void * ptr)
{
HeapFree(GetProcessHeap(), 0, ptr);
}
void * operator new[] (size_t iSize) {
void* ptr = HeapAlloc(GetProcessHeap(), 0, iSize); /* Why were we initializing the memory to zeros here? This is just a waste of cpu! */
if (!ptr)
throw std::bad_alloc();
else
return ptr;
}
void operator delete[] (void* ptr)
{
HeapFree(GetProcessHeap(), 0, ptr);
}
|
