#3357 After call to LoadBootstrapperBAFunctions() m_m_fPrereq changes causing Prereq code to execute


I created a simple bundle using the Wix 3.8.722 and VS2010 setup project template. I added a MsiPackage, which happens to be the Wix 3.7 core.msi, only because it was available, to allow the bundle to compile.

<?xml version="1.0" encoding="UTF-8"?>
<Wix xmlns="http://schemas.microsoft.com/wix/2006/wi">
<Bundle Name="Bootstrapper1" Version="" Manufacturer="Test" UpgradeCode="7cb68ca2-5132-45dd-a938-67a6376f6e0e">
<BootstrapperApplicationRef Id="WixStandardBootstrapperApplication.RtfLicense" />

        &lt;!-- TODO: Define the list of chained packages. -->
        &lt;MsiPackage SourceFile="C:\Development\WiX\Msi_ToAnalyize\Wixtools37_cached\core.msi"
              InstallCondition="1=0"/>  <!-- Never install, just debug bundle initialization-->

This project is build on one PC using the released Wix 3.8.722 installed using the wix.exe setup. On a Windows 8 x64 test box with WinDbg installed and Wix 3.8.722 source and pdbs from the download site, installed, when I step into this bundle, I observe that after the call to LoadBootstrapprBAFunctions() at line 916 of:

I observe that m_fPrereq is a large positive value causing ParsePrerequisiteFromXml() to be executed, which seems wrong. When I watch the local variables while stepping into LoadBootstrapperBAFunctions() the address of CWixStandardBootstraperApplication gets changed to what appears to be uninitialized memory and all member values also change.


  • Anonymous - 2013-08-16

    It looks like there may be a problem with the wixstdba.pdb file. If I use the download pdb files the reported bug can be reproduced. If I build the code myself I can debug correctly.

  • Rob Mensching

    Rob Mensching - 2013-08-21
    • Status: open --> migrated

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks