Why debug occasionally brings up disassembly rather than Windows files?
CodeGuru Home VC++ / MFC / C++ .NET / C# Visual Basic VB Forums Developer.com
Results 1 to 5 of 5

Thread: Why debug occasionally brings up disassembly rather than Windows files?

Threaded View

  1. #1
    Join Date
    May 2002
    Posts
    1,723

    Why debug occasionally brings up disassembly rather than Windows files?

    On fairly rare occasions, when attempting to debug one of my MFC applications on VS 2010, a compilation error is encountered, and instead of bringing up the customary Windows or MFC file with a arrow pointing to the problem, a disassembly appears with an arrow pointing to one of the assembler instructions. Since Windows assembly language is hardly my forte, I do not know how to interpret the error. Furthermore, the Output usually indicates one or more 'first chance exceptions' but little more, and the Stack output usually quite sparse and often refers cryptically to some ntdll.dll!7c92a82c().

    How can I better define the compile error?

    Would someone kindly explain to me what's going on here? Thanks.
    Last edited by Mike Pliam; January 15th, 2013 at 03:46 PM.
    mpliam

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Windows Mobile Development Center


Click Here to Expand Forum to Full Width

This is a CodeGuru survey question.


Featured


HTML5 Development Center