Hi Dave,
>My problem is that on the Windows XP machine that I have
the application on I can no longer break into the debugger
using an "_asm { int 3 }". This code worked until I installed
Visual Studio .Net. The system I'm running this on has both
Visual Studio 6 and VS 2005 running on it.
_asm { int 3 } should works well with VS2005 on a XP machine. I have
performed some tests on this issue, my test machine also installed the VC6
and VS2003, there is no problem on my side.
In order to dig into this problem, would you please provide more
information on this issue?
Generally, the _asm { int 3 } will cause an unhandled Win32 exception, does
that exception occur while you test the program? If the exception occurred,
the system will prompt a dialog window for you to choose the debugger to
debug the program? Do these behaviors happen in your machine? If you not,
what happens on your side?
Thanks!
Best regards,
Gary Chang
Microsoft Online Community Support
=============== =============== =============== =====
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.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/subscripti...t/default.aspx.
=============== =============== =============== =====
This posting is provided "AS IS" with no warranties, and confers no rights.