I expect the problem is that ::GetMessage() never gets the
::PostQuitMessage() so it's just hanging around waiting. We need to do the
much harder, "Figure out what happned to the quit message that should have
exited ::GetMessage()" :(
On Mon, Mar 25, 2013 at 11:56 AM, Bob Arnson <b...@joyofsetup.com> wrote:
> On 25-Mar-13 14:49, Bruce Cran wrote:
> > On 25/03/2013 18:03, Rob Mensching wrote:
> >> My favorite way to debug is to start Burn under the debugger using
> >> Image Execution Option flags. gflags.exe makes it easy to set. For low
> >> level stuff I often use windbg.exe, but I believe you can hook Visual
> >> Studio in there too with the jit debugger.
> > I've already stepped through the code - it shows PostQuitMessage being
> > called. But I'm not sure what further debugging I can do to determine
> > why GetMessage isn't returning.
> You can use Process Explorer to get a dump of the process once it's
> hung; with OS symbols, it's possible to get an idea of the root problem
> from where it's stuck under GetMessage.
>
> --
> sig://boB
> http://joyofsetup.com/
>
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_mar
> _______________________________________________
> WiX-devs mailing list
> WiX-devs@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-devs
>
>
------------------------------------------------------------------------------
Own the Future-Intel® Level Up Game Demo Contest 2013
Rise to greatness in Intel's independent game demo contest.
Compete for recognition, cash, and the chance to get your game
on Steam. $5K grand prize plus 10 genre and skill prizes.
Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
