Discussion:
Step Over (F10) and Step Into (F11) also show assembler code
(too old to reply)
Roy Chastain
2007-01-03 13:56:51 UTC
Permalink
Visual Studio 2005 with SP1.
This is a new install of VS on a new system and VS 2005 SP1 was installed. This is the first time I have tried to debug managed
code since the new installation of VS and SP1.

Every time I do a Step Over or a Step Into (either by menu of F10/F11), the source gets the assembler displayed and only 1
INSTRUCTION is executed. I have found no way to make it run a line of C# at a time.

This code that it has source for. When the assembler is displayed it is displayed with the C# around it.

Have I missed a setting or is this a SP1 bug?

Thanks
-------------------------------------------
Roy Chastain
KMSYS Worldwide, Inc.
http://www.kmsys.com
Jeffrey Tan[MSFT]
2007-01-04 02:52:09 UTC
Permalink
Hi Roy,

Happy New Year!

I just setup a new Vista machine and installed VS2005 with SP1 on it. So I
created a console type in VS2005 to test your scenario. Below is the test
code:
namespace ConsoleTest
{
class Program
{
static void Main(string[] args)
{
int i = 3;
Console.WriteLine("abc");
}
}
}

I set a breakpoint on the first C# line and tried both F10 and F11 to step
the code, no "Disassembly" window will pop up with ASM code. Then I tried
to turn-on/off all the possible options(including Enable unmanaged code
debugging, Enable Address-Level debugging and Show disassembly if source is
not available) in VS2005 to see if I can reproduce the strange problem; F10
and F11 still step through the C# source code instead of ASM code.

Based on my experience, only if you manually open the "Disassembly" window
by choosing "Go to Disassembly" option and press F10/F11 in "Disassembly"
window, will the debugger step through the ASM code list. If you press
F10/F11 in *.cs C# source code file, debugger will always step through the
C# code statement.

Is it possible for you to provide a little sample project to demonstrate
the problem? I also recommend you provide the detailed steps to reproduce
this problem. This information would be helpful for us to understand this
problem. 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.
Roy Chastain
2007-01-08 11:10:45 UTC
Permalink
Jeffery,
It appears to be inconsistent. Today if I step through with F10 and F100 it works as it should. I also think that it work
correct the day after I made the original posting, but on Friday, it went into instruction mode after a exception was caught.

For now, lets just ignore this issue and, if it persists, I will try to figure out a pattern or something.

Mostly I just wanted to see if this was an SP1 related issue.

Thanks
Post by Jeffrey Tan[MSFT]
Hi Roy,
Happy New Year!
I just setup a new Vista machine and installed VS2005 with SP1 on it. So I
created a console type in VS2005 to test your scenario. Below is the test
namespace ConsoleTest
{
class Program
{
static void Main(string[] args)
{
int i = 3;
Console.WriteLine("abc");
}
}
}
I set a breakpoint on the first C# line and tried both F10 and F11 to step
the code, no "Disassembly" window will pop up with ASM code. Then I tried
to turn-on/off all the possible options(including Enable unmanaged code
debugging, Enable Address-Level debugging and Show disassembly if source is
not available) in VS2005 to see if I can reproduce the strange problem; F10
and F11 still step through the C# source code instead of ASM code.
Based on my experience, only if you manually open the "Disassembly" window
by choosing "Go to Disassembly" option and press F10/F11 in "Disassembly"
window, will the debugger step through the ASM code list. If you press
F10/F11 in *.cs C# source code file, debugger will always step through the
C# code statement.
Is it possible for you to provide a little sample project to demonstrate
the problem? I also recommend you provide the detailed steps to reproduce
this problem. This information would be helpful for us to understand this
problem. 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.
-------------------------------------------
Roy Chastain
KMSYS Worldwide, Inc.
http://www.kmsys.com
Jeffrey Tan[MSFT]
2007-01-09 06:55:22 UTC
Permalink
Hi Roy,

Thank you for feedback the status.

Yes, this type of inconsistent problem is really hard to troubleshoot.
Anyway, if you figure out the reproduce pattern, please feel free to post.
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.
Loading...