Empty messages from MFC
-
While I usually try to avoid any message boxes that do not stem from my own code, I now am facing a box that comes from MFC, but the weird thing is that it is empty... which is not that helpful. I stumbled upon this a few times during testing, but never cared since I removed the various DDV_XXX functions later that caused those boxes. This only happens in Release build, which uses statically linked MFC, so I suppose it has something to do with that... Is there any way to get some more meaningful message boxes with statically linked MFC?
-
While I usually try to avoid any message boxes that do not stem from my own code, I now am facing a box that comes from MFC, but the weird thing is that it is empty... which is not that helpful. I stumbled upon this a few times during testing, but never cared since I removed the various DDV_XXX functions later that caused those boxes. This only happens in Release build, which uses statically linked MFC, so I suppose it has something to do with that... Is there any way to get some more meaningful message boxes with statically linked MFC?
Do you use custom DDV processing? Can you post the DDV code that causes this? What VS version?
Best wishes, Hans
-
While I usually try to avoid any message boxes that do not stem from my own code, I now am facing a box that comes from MFC, but the weird thing is that it is empty... which is not that helpful. I stumbled upon this a few times during testing, but never cared since I removed the various DDV_XXX functions later that caused those boxes. This only happens in Release build, which uses statically linked MFC, so I suppose it has something to do with that... Is there any way to get some more meaningful message boxes with statically linked MFC?
Daniel 'Tak' M. wrote:
I now am facing a box that comes from MFC
What do you mean by this? I don't think you will get random message boxes without writing some code.
Daniel 'Tak' M. wrote:
I stumbled upon this a few times during testing, but never cared
Big mistake.
I must get a clever new signature for 2011.
-
While I usually try to avoid any message boxes that do not stem from my own code, I now am facing a box that comes from MFC, but the weird thing is that it is empty... which is not that helpful. I stumbled upon this a few times during testing, but never cared since I removed the various DDV_XXX functions later that caused those boxes. This only happens in Release build, which uses statically linked MFC, so I suppose it has something to do with that... Is there any way to get some more meaningful message boxes with statically linked MFC?
I suggest you follow the tried and true and procudure of getting a stack trace when the problem occurs. You may want to alter the settings for the release build so that a pdb file is built (so you get a more meaningful stack).
Steve
-
Do you use custom DDV processing? Can you post the DDV code that causes this? What VS version?
Best wishes, Hans
No and no; the VS version is 2005. If I knew where exactly this errors pops ups, I'd be much further... I am also not sure if it is a DDV call, since I barely use them.
-
I suggest you follow the tried and true and procudure of getting a stack trace when the problem occurs. You may want to alter the settings for the release build so that a pdb file is built (so you get a more meaningful stack).
Steve
My main problem is not to find out where it occurs, the main problem is why all warnings and errors from MFC are empty... It doesn't happen only this one time, it happens for every DDV call as well, for example, and I'd really prefer some more meaningful message boxes (crazy, I know). Is there, for example, a resource DLL that has to be shipped with my program so that MFC can load its error messages properly? Something like that...
-
My main problem is not to find out where it occurs, the main problem is why all warnings and errors from MFC are empty... It doesn't happen only this one time, it happens for every DDV call as well, for example, and I'd really prefer some more meaningful message boxes (crazy, I know). Is there, for example, a resource DLL that has to be shipped with my program so that MFC can load its error messages properly? Something like that...
Daniel 'Tak' M. wrote:
Is there, for example, a resource DLL
If you create a standard MFC app and choose the defaults, you will see that "afxres.rc" is included in the project's .rc file.
Best wishes, Hans