Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. Visual Studio
  4. Thread exits after break point

Thread exits after break point

Scheduled Pinned Locked Moved Visual Studio
csharpdebuggingquestion
2 Posts 1 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M Offline
    M Offline
    MaxRelaxman
    wrote on last edited by
    #1

    Okay this is weird. I'm running VS2005 and I have a breakpoint set inside a thread. When I try to step into or step over the code, the thread exits with execution result of 0 (0x0) Actual Message: The thread '' (0xcdc) has exited with code 0 (0x0) If I remove the breakpoint, a later breakpoint hits fine (meaning the previous code executed okay) but again I cannot step into or step over the code. This code was debugging fine yesterday. Does anyone have any idea what I've done wrong? Thanks! EDIT: I should probably mention that the code in is C#

    M 1 Reply Last reply
    0
    • M MaxRelaxman

      Okay this is weird. I'm running VS2005 and I have a breakpoint set inside a thread. When I try to step into or step over the code, the thread exits with execution result of 0 (0x0) Actual Message: The thread '' (0xcdc) has exited with code 0 (0x0) If I remove the breakpoint, a later breakpoint hits fine (meaning the previous code executed okay) but again I cannot step into or step over the code. This code was debugging fine yesterday. Does anyone have any idea what I've done wrong? Thanks! EDIT: I should probably mention that the code in is C#

      M Offline
      M Offline
      MaxRelaxman
      wrote on last edited by
      #2

      Nevermind, I solved the problem. (I moved the class initialization into a method of the calling class rather than doing class Blah = new Blah() when declaring it as a property)

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups