Hi,
I'm working with the latest WIX version (v3.6.3206.0).
Unhandled exception at 0x0FF45EE6 (wixstdba.dll) Setup.exe: 0xC0000005:
Access violation reading location 0x00000018.
After downloading the symbols from Wixtoolset.org, Visual Studio pinpointed
the exception to WixStandardBootstrapperApplication.cpp, line 558:
virtual STDMETHODIMP_(int) OnExecutePackageBegin(
__in_z LPCWSTR wzPackageId,
__in BOOL fExecute
)
{
if (wzPackageId && *wzPackageId)
{
BAL_INFO_PACKAGE* pPackage = NULL;
HRESULT hr = BalInfoFindPackageById(&m_Bundle.packages,
wzPackageId, &pPackage);
LPCWSTR wz = (SUCCEEDED(hr) && pPackage->sczDisplayName) ?
pPackage->sczDisplayName : wzPackageId;
m_fShowingInternalUiThisPackage = pPackage->fDisplayInternalUI;
// Error occurs in this line
ThemeSetTextControl(m_pTheme,
WIXSTDBA_CONTROL_EXECUTE_PROGRESS_PACKAGE_TEXT, wz);
ThemeSetTextControl(m_pTheme,
WIXSTDBA_CONTROL_OVERALL_PROGRESS_PACKAGE_TEXT, wz);
}
else
{
m_fShowingInternalUiThisPackage = FALSE;
}
return __super::OnExecutePackageBegin(wzPackageId, fExecute);
}
When I try to peek into the members of pPackage, the debugger says "Unable
to read memory". I can peek into other objects without problems.
The line in question was introduced in version v3.6.3130.0, and I guess it's
missing a guard condition. If hr is E_NOTFOUND, pPackage will be null and
the whole thing crashes.
Kind regards,
Henning
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
