Yes I had a similar problem setting a breakpoint, but I did not realize it was due to the pdb. When WinDbg launches the exe it breaks and gives me a chance to set a breakpoint. I would not show the breakpoint that I tried to set with F9 after placing the cursor at LoadBootstrapperBAFunctions() (or prior to that call). However after I pressed F5 to start execution then the breakpoint took effect at the point at which I had previously pressed F9. The next time I launched the exe with WinDbg it would not show the existing breakpoint, but if I pressed F5 it would then show the existing breakpoint and break. So while that was different than my other experiences using WinDbg I did not realize that it was related to the pdb file.
Having said that, I agree with your plan to close this bug, and if I learn more information I will provide it. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WixStdBA-LoadBootstrapperBA-changes-m-fPrereq-tp7588034p7588176.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
