CodeGuru Home VC++ / MFC / C++ .NET / C# Visual Basic VB Forums Developer.com
Results 1 to 6 of 6
  1. #1
    Join Date
    May 1999
    Posts
    156

    Debug break point in VC 5.0

    Hi,

    I am using VC 5.0. I encounter an annoying problem when debugging my program. I set break point by 'F9'. Most of the time it works and I can set break point on any executable statement I like. However, it sometime gives me an error in a dialog box when I start debug. The dialog says something like cannot set break point and program start at the beginning. It turns my break point from a brown dot to a white filled hollow dot.

    Can someone tell me why I can't set 'that' particular break point. There must be rules but I don't know where to find. Please help.

    Will


  2. #2
    Join Date
    May 1999
    Posts
    44

    Re: Debug break point in VC 5.0

    Are U sure U are in debug mode when U encounter this problem?.


  3. #3
    Join Date
    May 1999
    Posts
    156

    Re: Debug break point in VC 5.0

    Sadly so, yes. As I said, it does not always come (the dialog) but when it does, sometime I can get rid of it by put the break point in another valid line. Does it sound like a misconfiguration or bug of VC 5.0 ?

    Will


  4. #4
    Join Date
    May 1999
    Location
    OR, USA
    Posts
    65

    Re: Debug break point in VC 5.0

    This happens because the debugger cannot find the machine-code equivalent
    of ur source code. See if 'Rebuild all' heps


  5. #5
    Join Date
    May 1999
    Location
    Toronto, Ontario, Canada
    Posts
    155

    Re: Debug break point in VC 5.0

    If you are debugging a DLL, make sure it is in the "Project Settings" -> "Debug" -> Category "Additional DLLs".

    -Safai

  6. #6
    Join Date
    Apr 1999
    Posts
    27,449

    Re: Debug break point in VC 5.0

    Here are a few possibilities:

    - You're running the release version with no debug info.

    - Source is out of date. Lines have been moved/erased/added, and you didn't do a recompile.

    - Optimizations have been set on. When debugging optimized code, some lines get moved or eliminated by the compiler.

    - Debug mode was not on for the compiled module. This could mean the debug settings were not set correctly in the Project | Settings.

    - Source module is part of an external library (i.e. DLL or static LIB file) that was built with no debug info.

    Regards,

    Paul McKenzie


Posting Permissions

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





Click Here to Expand Forum to Full Width

Featured