memory breakpoints/buffer overflows in the VC++ 2005 debugger

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Jonathan Wilson

    #1

    memory breakpoints/buffer overflows in the VC++ 2005 debugger

    I have an app written in native C++ using Visual C++ 2005 (pro edition).
    How can I set a memory breakpoint in the debugger for this app?
    Or alternatively, is there another source level debugger I can use that
    will let me set such breakpoints?

    Note that moving to Visual Studio 2008 is not an option.
  • Bob Altman

    #2
    Re: memory breakpoints/buffer overflows in the VC++ 2005 debugger

    Does VS 2008 have this feature?

    Way back in my VAX/VMS days, the debugger had a feature called a "watch
    point", which would break into the debugger when data at a specified memory
    address was modified. The debugger did this by write protecting the page
    containing the watch point, then handling the resultant access violations,
    completing those that don't involve the watch point and breaking into the
    debugger on those that do.

    Bob

    "Jonathan Wilson" <jfwfreo@tpgi.c om.auwrote in message
    news:uW7LkLJcIH A.5160@TK2MSFTN GP05.phx.gbl...
    >I have an app written in native C++ using Visual C++ 2005 (pro edition).
    >How can I set a memory breakpoint in the debugger for this app?
    Or alternatively, is there another source level debugger I can use that
    will let me set such breakpoints?
    >
    Note that moving to Visual Studio 2008 is not an option.

    Comment

    • Jochen Kalmbach [MVP]

      #3
      Re: memory breakpoints/buffer overflows in the VC++ 2005 debugger

      Hi Jonathan!
      I have an app written in native C++ using Visual C++ 2005 (pro edition).
      How can I set a memory breakpoint in the debugger for this app?
      Or alternatively, is there another source level debugger I can use that
      will let me set such breakpoints?
      Start your project in the debugger. Set some breakpoint where the
      variable is accessible.
      Then in the menu:
      Debug|New Breakpoint|New Data Breakpoint...

      The specify either the address or the variable name.

      Depending on the processor, normally 4 data breakpoints are natively
      supported.

      PS: Memory(Data)-Breakpoints are a avilable since several years in VS...


      --
      Greetings
      Jochen

      My blog about Win32 and .NET

      Comment

      Working...