CPropertyPage constructor causes crash when using the DLL version MFC 7.1 - by Martin Richter

Status : 

  Not Reproducible<br /><br />
		The product team could not reproduce this item with the description and steps provided.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


2
0
Sign in
to vote
ID 270493 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 4/12/2007 12:29:21 PM
Access Restriction Public

Description

m_psp member in a CPropertyPage is allocated as requested but the dwSize member is always overwritten when one of the following constructors is used
 CPropertyPage(UINT nIDTemplate, UINT nIDCaption, UINT nIDHeaderTitle, UINT nIDHeaderSubTitle = 0, DWORD dwSize = sizeof(PROPSHEETPAGE));
CPropertyPage(LPCTSTR lpszTemplateName, UINT nIDCaption, UINT nIDHeaderTitle, UINT nIDHeaderSubTitle = 0, DWORD dwSize = sizeof(PROPSHEETPAGE)); 
Sign in to post a comment.
Posted by Martin Richter on 4/25/2007 at 9:31 AM
It is unbelievable for me that you can not repro this. It is 100% obvious that the constructor destorys the internal dwSize member in MFC71.DLL!

OK! I just uploaded PropPageBug3.

Please compile a release version of this program.
Please select basic test in the Application Verifier for this!

Launch the program and press the Test button. The application will crash!

Every program that uses a CPropertyPage with this constructor must fail the "Certified for Vista" Tests!
Posted by Microsoft on 4/22/2007 at 8:07 PM
Thanks for your feedback. However, the site only accepts feedback for Microsoft .Net Framework 2.0/3.0 and Visual Studio 2005/Orcas product related issues. For more help, please call support directly (see http://support.microsoft.com).

Thank you,
Visual Studio Product Team.
Posted by Microsoft on 4/12/2007 at 7:32 PM
Thanks for your feedback. However, the site only accepts feedback for Microsoft .Net Framework 2.0/3.0 and Visual Studio 2005/Orcas product related issues.

Thank you,
Visual Studio Product Team.
Posted by Microsoft on 4/12/2007 at 5:28 PM
Thank you for your feedback. We are currently investigating. If this issue is urgent, please call support directly (see http://support.microsoft.com).

Thank you,
Visual Studio Product Team