Ram/vram

Lionmane · Oct 30th 2005, 1:16pm

Hi!

I'm trying to get the memory checking program to work in Chapter 5 (page 134).

I'm getting some weird errors though...

Some of the errors I fixed by adding #include <windows.h> at the top.

Now I'm down to four errors. The first of which is "syntax: missing ';' before 'type'" on the line that says:

char *buff = GCC_NEW char[virtualRAMNEEDED];

The only other changes I've made to the code is substituting a message box where it says "throw GameCodeError".

First off, I *know* I don't have any missing semicolons and MSVC++ ver 6.0 is obviously senile. Secondly, I've double checked my code to make sure it matched the book (other than the #include and message boxes).

Am I doing something wrong? I didn't see anything about that program on this website...

Thanks!

mw

Larrik · Oct 30th 2005, 2:07pm

It doesn't seem to like the "GCC_NEW" part. I don't have a copy of the code installed to go looking, but that's where I'd start.

Oh, and the code doesn't really work with VC++6.0

Lionmane · Oct 30th 2005, 2:36pm

WinAPI code doesn't work with MSVC++?!?!?!

What the heck?!

WINDOWS API code doesn't work with MICROSOFTVC++?!?!?!

Oh, wait... It's Microsoft. Microsoft products only work in a Linux environment!

I Googled GCC_NEW but didn't find anything particularly useful. One website seemed to suggest it was a replacement for malloc()...

What is GCC_NEW for?

mw

Sabrina · Oct 30th 2005, 7:40pm

Hi,

"GCC_NEW" is a macro the autor has defined in his
release code. (GameCodeStd.h).

.
.
#if defined(_DEBUG)
# define GCC_NEW new(_NORMAL_BLOCK,__FILE__, __LINE__)
#else
# define GCC_NEW new
#endif
.
.

S.

DarkPenguin · Oct 30th 2005, 7:48pm

Originally posted by Sabrina
"GCC_NEW" is a macro the autor has defined in his
release code. (GameCodeStd.h).

Ditto, check if you have the right include. The semicolon error looks like it's not seeing GCC_NEW right.

Lionmane · Oct 30th 2005, 8:35pm

What exactly does it do?

mw

Nebuchadnezzar · Oct 30th 2005, 9:42pm

Source Code

#if defined(_DEBUG)
# define GCC_NEW new(_NORMAL_BLOCK,__FILE__, __LINE__)
#else
# define GCC_NEW new
#endif

Looks like, if _DEBUG is defined it sets the GCC_NEW macro to call a new() macro that manages some debug information for tracking memory allocation errors, and if _DEBUG is not defined it sets the GCC_NEW macro to be the same as the 'new' keyword.

Kain · Oct 31st 2005, 12:20pm

Yeah... it's basically a good practice to overwrite the new operator for debugging purposes to catch those pesky memory leaks.

Lionmane · Oct 31st 2005, 8:20pm

It's ok now. I just looked up GlobalMemoryStatus on MSDN and used the sample program there.

Thanks anyway though!

mw

jediboy · Sep 24th 2008, 2:48am

Hi guys,

If you don't like overloading the new operator, you could check out Dan Moulding's Visual Leak Detector.

dmoulding.googlepages.com/vld

Just include a header and lib, and it will keep track of the CRT allocations internally, and report them to you via the output dialog.

Now if only there was a COM leak tool like this...

Regards,
B.

Ram/vram

Ram/vram

RE: Ram/vram

RE: Ram/vram

RE: Ram/vram

RE: Ram/vram

RE: Ram/vram

Source Code

Share