Hi,

When I debug unmanaged C++ and put breakpoints say in system modules such as
kernel32, when I restart the application the breakpoints get disabled and I
have to re-enable them manually. How can I make Visual Studio 2005 not to
disable the breakpoints, or re-enable them automatically?

Thanks

--

Hi Muriwai,

Sorry for letting you wait.

After doing some research, it seems that this is a known issue of VS2005.
The VS debugger team does this by design. See the bug report below:
https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?Feedba
ckID=101569

The debugger team deliberate changes this behavior from VS.net2003 due to
the danger associated with address breakpoints being reused from one
session to another. If you do not like it, you have to write a macro to
enable the breakpoints during opening.

Thanks.

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Muriwai,

I will spend some time to reproduce your problem on my side, I will get
back to you ASAP. Thanks.

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Thanks Jeffrey. I am aware of the "danger". The debugger misbehaves when a
breakpoint becomes in the middle of a CPU instruction when the code changes
between the sessions. Though the debugger could do something more smarter
than simply disabling the breakpoints. For example, it could remember the
code bytes around the breakpoint and disable the latter only when the code
changes.

Cheers


--

[quoted text, click to view]

Hi Muriwai,

Thanks for your suggestion. Yes, I have discussed this with the VS debugger
developer, below is his feedback:

"It certainly the case that we could have added a heuristic here. We went
with this because it was easy, consistent, and safe. You are certainly free
to open a suggestion bug, but even if we fix it, it will be a while (too
late for Orcas).

One tip: depending on what you are trying to do, you may be able to use
function breakpoints instead. These persist between debug sessions (or
computers, or operating system versions)."

If you would like submit the suggestion, you may submit it in the link
below, the debugger team will file it in the internal database for future
consideration:
https://connect.microsoft.com/VisualStudio?wa=wsignin1.0

Hope this helps.

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.