Debugger disappears

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Aads
    New Member
    • Mar 2008
    • 48

    Debugger disappears

    Hi all,

    I'm working on a C#.NET windows application which comprises of 80 projects under a single solution & the application is based on CAB (Composite Application Blocks). The problem I face is that the debugger disappears most of the times during debugging. I'm running out of my patience because of this problem. By the way, I'm using Visual Studio 2008 IDE.

    I've got to admit that it is a multithreaded application.

    Any help is greatly appreciated.

    Regards,
    Aads
  • Plater
    Recognized Expert Expert
    • Apr 2007
    • 7872

    #2
    What do you mean the debugger dissapears?
    The IDE closes?

    Comment

    • Aads
      New Member
      • Mar 2008
      • 48

      #3
      Hi Plater,

      Thanks for your quick reply.

      When I debug the application the control advances to the next statement as it should, but after a gap of some time, say for example 40 seconds, the application pauses for 5 seconds & then both the debugger & the application disappears.

      When I say debugger I mean the yellow highlighted line that moves when I press F10/F11 & when I say application it means the exe that is opened as a result of executing the code (i.e. the exe that opens when you press F5).

      In my case, both of them gets disappeared & I can only see the source code (IDE) remaining "alive"! However, the debug toolbar button (corresponding to the F5 action) is disabled (greyed out) which means the code is still running but the application is not!

      Please let me know in case it is not clear to you.

      Thank you.

      Regards,
      Aads

      Comment

      • Plater
        Recognized Expert Expert
        • Apr 2007
        • 7872

        #4
        This happens when the application gets stuck processing events or doing low level I/O or a COM object is taking up the time or otherwise in an infinite loop.
        If you go to debug->break, you will see the line it got stuck on, probably the last line you saw in yellow.

        When this sort of things happens, it generally means you have a bug in your code.

        Comment

        Working...