Скачать или смотреть Memory Validator - broken message map detection

0:01 Hello, I'm going to show you how to detect broken message maps using C memory validator and Visual Studio 6.

0:09 This doesn't apply to Visual Studio 7 and above because you cannot create a broken message map with Visual Studio 7 and above.

0:16 So first of all, we need to start by changing the settings.

0:19 So we click on the toolbox icon to display the settings dialog.

0:23 Now go to MFC message map checks and select the checkbox on that page and click the OK button.

0:32 Now we need to start the example application by clicking the relaunch icon.

0:37 All the message maps in your application are now hooked and they will be monitored as your application executes.

0:43 Example application started and bring that to the front.

0:46 On the memory errors menu, I'm going to choose message map error.

0:50 And there you go.

0:51 Memory Validator has found the error.

0:52 It's displayed a warning box with abort, retry and ignore.

0:56 Across the bottom and you can see the call stack at the bottom.

1:00 And up at the top, there is actually the line where the errors occurred.

1:05 That's a test VW line 6456.

1:10 And the function is OnMemoryerrorsMessagemaperror.

1:13 That function has an incorrect message map signature.

1:16 It more than likely has the wrong return type or an incorrect number of arguments.

1:22 And this means that when the function is called, the function gets executed, but when the function returns, the stack is in the wrong place. And that will quite often work in a debug program, but

1:32 you'll get random crashes in release programs.

1:34 That really doesn't help you.

1:37 Thank you very much