the old debugger-fixes-your-problem-but-does-say-a-peep trick

I discovered why a program of mine has been crashing

Code:

---

Char* ret = new Char[size];

---

At first I thought size was overflowing the memory, but my showHex func reveals that it's only 14. A memory leak I was thinking, but the line

Code:

---

Char ret[140];

---

works just fine in it's place, and it's allocating 10 times the space.

So time to use the debugger I thought, but when I run it through the debugger, NOTHING happens, go back to normal build, it crashes again. Somehow the debugger is fixing this problem, but it doesn't report any error or warning of any kind.

What going on?

I'm using dev btw

Who knows? It could be anything. I'm betting on a buffer overrun, though, if allocating more space works.

What if you still use dynamic memory allocation, but get more space than you need?

Code:

---

Char* ret = new Char[size * 10];

---

This thread is turning out to be pretty useful. :) http://cboard.cprogramming.com/showthread.php?t=105440

No no, the actual call to new is what's crashing, not the writing to of it's returned elements.

Do you try and catch std::bad_alloc after the new statement? Should throw an exception of the type bad_alloc if it fails? I think...

> No no, the actual call to new is what's crashing
In which case, the problem is somewhere else.

Some other user of allocated memory is doing something wrong, say
- use after free
- double free
- buffer overrun (or underrun)

Post the code for the function.