rbuchana

Alright lets find the true windows gurus here.

I wrote a WTL dialog that models a RF detector.

Sometimes when I run it I get a message stating a heap corruption. It says I wrote over the heap buffer.

Does this mean I overwrote the end of a dynamically allocated array? I don't think so, because if it was it would throw a different type of message.

Am I actually using up all the memory windows is allocating for my program?

And how do I debug it?

edwinsmith

OK, I'm a little rusty here. What's a WTL dilog? I write machine code for 8051's and I also do some C# .NET stuff. The compiler usually takes care of that stuff.

The Heap is your memory area for variables. What it sounds like is you've got a stack overrun because of to many pushes and not enough pops. Check that you're not doing a recursive loop or some other strangeness like doing a jump out of a subroutine.

Edwin

grantx5

Here's a little help. As the article states heap corruption is a BIG topic and involves many things.


http://www.windowsitpro.com/Web/Arti...275/22275.html


Bottom-line, memory is being mishandled.

rbuchana

assertions are my friend. I was writing past the end of a dynamically allocated array. I try to be diligent in my assertions but obviously I missed a crucial one. Thanks guys.

Totallyrad

It's not that hard, just open the windows and throw the computer out.

oscaroc

Are you fellows speaking a foriegn language or Have I had enough to drink for tonight?

Totallyrad

Affirmitive

rbuchana

It's english to me, but i guess I'm the minority.....

MasseyMan1089

Umm, I've got a perfect solution to all your problems! System restore to an earlier point. haha. Hope you fix your errors anyways...