C / C++ / MFC

CWnd* p = GetDlgItem(IDCANCEL);
p->EnableWindow(FALSE);

HWND h = ::GetDlgItem(hYourDlgHandle, IDCANCEL);
::EnableWindow(h, FALSE);

James R. Twine wrote:

I believe that the STL string object will not allocate storage until required or directly requested. So #3 should not be expected to throw an exception.

James R. Twine wrote:

heap corruption

James R. Twine wrote:

address space exhaustion

George_George wrote:

I am using Visual Studio. I am interested to find more information about whether in my specific version of STL implementation, for empty string, whether there will be any space allocation. But in file string, there is no constructor for basic_string. Do you know where to find it? (I believe I should look at the constructor for string, which is the same as the constructor for basic_string)

George_George wrote:

Is it structured exception or C++ exception? I belive it is structured exception. But I am talking about C++ exception.

George_George wrote:

You mean we reserved a lot of space in virtual memory, but not commit?

James R. Twine wrote:

I am not sure which version of VS you are talking about, but I am sure a simple find in files will locate it for you.

James R. Twine wrote:

AFAIK, that would depend on the type of heap corruption. Your heap could br corrupted such that it thinks that there are no more free blocks avaialble (if you use a non-growable heap), or its internal structured could be fulblungered such that when the heap code tries to use/evaluate them, it causes a crash.

George_George wrote:

I think you mean some meta data of heap, e.g. free space size of the heap is corrupted (so that the actual free memory size is not reflected), then when we allocate later, there will be bad_alloc exception?

rowdy_vc++ wrote:

As my code is C++..

rowdy_vc++ wrote:

Is there any DLL corruption or not?If it is yes what kind of DLL add that problem ..?