|
|
You're in the
visual studio .net debugging
group:VB Compiler Error in VS2005 Team Dev
visual studio .net debugging:
Hi,
I am debugging a project that contains ADO.NET datasets. When I hit a breakpoint, and press F11 to step into the process, I consistently get a VB compiler error whenever my debugging takes me into the dataset designer code file, where the <System.Diagnostics.DebuggerNonUserCode()> attribute lives. My understanding was that this attribute would cause the debugger to step through the code, as per these remarks: "Designer provided types and members that are not part of the code specifically created by the user can complicate the debugging experience. This attribute suppresses the display of these adjunct types and members in the debugger window and automatically steps through, rather than into, designer provided code. When the debugger encounters this attribute when stepping through user code, the user experience is to not see the designer provided code and to step to the next user-supplied code statement." This does not seem to be the case for me. The error is so bad, that I get prompted to send error reports to Microsoft and have to use task manager to kill the IDE. Then I have to restart my machine! Is there a way to avoid this behavior? Thanks. --
Hi John,
Can you provide the detailed error information regarding your problem? A screen shoot would be helpful for us to understand the scenario. With the error message, I can perform some search in our database and find out if this is a known issue. Thanks. Additionally, what type project do you encounter this error, Winform or Asp.net project? Can this VS2005 crash occur in a new sample project? If you have the definite steps to reproduce this problem or even a simple reproduce project, please feel free to provide the steps or the project to me. I look forward to hearing from you. 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 John,
Have you reviewed my reply? How about your problem now? If you have any concern or need any help, please feel free to feedback. 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 John,
Sorry for the striking reply, I almost missed your email in the mailbox. I will perform some research for this issue and 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.
Hi Henin,
After performing some search, I find several reported issues regaridng this error. It seems that it is caused by VB background compiler thread exception crash. Please refer to the 2 records below: http://lab.msdn.microsoft.com/ProductFeedback/viewFeedback.aspx?feedbackid=4 98056cb-7e44-4ee0-9da8-7776106a0726 http://lab.msdn.microsoft.com/ProductFeedback/viewfeedback.aspx?feedbackid=9 c9c9185-e305-426d-be7c-1f0e01bec62e The first one is caused by VSS, while the second one really a bug which using a lot of parameters for attribute's constructor. You may check to ensure if your problem is the same as these 2 issues. 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.
Neither of these describes my issue. I will try to put together a simple
demo to reproduce using NW database this weekend. -- John [quoted text, click to view] ""Jeffrey Tan[MSFT]"" wrote:
> Hi Henin, > > After performing some search, I find several reported issues regaridng this > error. It seems that it is caused by VB background compiler thread > exception crash. Please refer to the 2 records below: > > http://lab.msdn.microsoft.com/ProductFeedback/viewFeedback.aspx?feedbackid=4 > 98056cb-7e44-4ee0-9da8-7776106a0726 > http://lab.msdn.microsoft.com/ProductFeedback/viewfeedback.aspx?feedbackid=9 > c9c9185-e305-426d-be7c-1f0e01bec62e > > The first one is caused by VSS, while the second one really a bug which > using a lot of parameters for attribute's constructor. You may check to > ensure if your problem is the same as these 2 issues. > > 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 Henin,
Thanks for your effect of creating a sample demo project. Actually, I can find many records in our internal database for following keywords: "Visual Basic compiler" encountered problem "internal compiler error" recover HC0000005 However, no one in these records is specific with F11 single stepping or DebuggerNonUserCode. So without a reproducing project and just with the shootscreen and current information, it is hard for us to troubleshoot the root cause. Thanks for your understanding. I will wait for your demo project to investigation. Thanks for your patient. 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 Jeff,
Please check your mailbox for a sample project that I sent to you this morning. -- John [quoted text, click to view] ""Jeffrey Tan[MSFT]"" wrote:
> Hi Henin, > > Thanks for your effect of creating a sample demo project. > > Actually, I can find many records in our internal database for following > keywords: > "Visual Basic compiler" encountered problem "internal compiler error" > recover HC0000005 > > However, no one in these records is specific with F11 single stepping or > DebuggerNonUserCode. So without a reproducing project and just with the > shootscreen and current information, it is hard for us to troubleshoot the > root cause. Thanks for your understanding. > > I will wait for your demo project to investigation. Thanks for your patient. > > 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. >
Hello John,
Thanks for your reply. Jeffery has been absent today and I'll help monitor this issue and inform Jeffery as soon as he've come back. Meanwhile, if you have any further finding or comments, please feel free to post here also. Thanks for your understanding. Sincerely, Steven Cheng Microsoft MSDN Online Support Lead This posting is provided "AS IS" with no warranties, and confers no rights.
Hi John,
Sorry for letting you wait, I am sick at home for 2 days :-( Yes, I have received your sample project in mailbox. Below is my analysis process regarding your project: 1. After unzipping your project, I openned it and tried to debug it by pressing F5 in VB2005 IDE. Then I got an unhandled exception in the "Me.Adapter.Fill(dataTable)" in "GetData()" method of DataSet1.Designer.vb file. Also, the VB2005 IDE will pop up the "Microsoft (R) Visual Basic Compiler has encountered a problem and needs to close. We are sorry for the inconvenience." crash dialog. By using "Process Explorer", I can see that this dialog(Microsoft Application Error Reporting process) is actually started by VB2005 IDE exception handler, see the call stack below: msvb7.dll!CreateDWProcess+0xea msvb7.dll!WatsonFilter+0x4d msvb7.dll!DoFilterException+0x24 msvb7.dll!CompilerProject::GetCurrentActiveStatementPosition+0x78 msvb7.dll!_EH4_CallFilterFunc+0x12 msvb7.dll!_except_handler4+0x8e ntdll.dll!ExecuteHandler2+0x26 ntdll.dll!ExecuteHandler+0x24 ntdll.dll!KiUserExceptionDispatcher+0xe In the details information from the Microsoft Application Error Reporting dialog, I can find that the unexpected exception is 0xC0000005, which is Access Violation exception. Then, I tried to load windbg to debug this Access Violation in VB2005 IDE. I got the following full call stack(sorry the call stack is really too long): (2c4.714): Access violation - code c0000005 (first chance) First chance exceptions are reported before any exception handling. This exception may be expected and handled. eax=00000000 ebx=0000000c ecx=0ad2e500 edx=001ba046 esi=12cc0064 edi=09bf248c eip=598afb2b esp=0012d6b0 ebp=00000274 iopl=0 nv up ei pl nz na po nc cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010202 msvb7!ENCBuilder::GetCurrentActiveStatementPosition+0x53: 598afb2b 8b8040020000 mov eax,dword ptr [eax+240h] ds:0023:00000240=???????? *** WARNING: Unable to verify checksum for C:\WINDOWS\assembly\NativeImages_v2.0.50727_32\mscorlib\4fe66c7733005e4fbfe3 7c4f11e3cd76\mscorlib.ni.dll 0:000> kL 50 ChildEBP RetAddr 0012d6dc 598afa93 msvb7!ENCBuilder::GetCurrentActiveStatementPosition+0x53 0012d71c 5d7335d5 msvb7!CompilerProject::GetCurrentActiveStatementPosition+0x84 0012d734 5d743560 msvbprj!CVbBldCompiler::GetCurrentActiveStatementPosition+0x44 0012d744 54cf6eb8 msvbprj!CVsProjHierarchy::GetCurrentActiveStatementPosition+0x42 0012d7b4 54bb4791 encmgr!CEncMgr::CurrentPositionFromOriginal+0x14c 0012d84c 54c27e8e vsdebug!CTextPos::SetTextPositionFromDocumentContext+0x156 0012d878 79f21268 vsdebug!CDebugger::ShowSource+0x5c 0012d988 014ea7ca mscorwks!CLRToCOMWorker+0x196 0012da04 13f46dc4 CLRStub[StubLinkStub]@14ea7ca 0012da40 13f4494d Microsoft_VSDesigner!Microsoft.VSDesigner.ExceptionAssistant.CodeEditorCoope rator.OpenDocumentWindow(Microsoft.VSDesigner.ExceptionAssistant.ExceptionIn fo)+0x34 0012da90 13f4451b Microsoft_VSDesigner!Microsoft.VSDesigner.ExceptionAssistant.DebuggerMonitor ..NewAssistantWindow(Microsoft.VSDesigner.ExceptionAssistant.ExceptionInfo, Boolean)+0x145 0012dac0 51a45504 Microsoft_VSDesigner!Microsoft.VSDesigner.ExceptionAssistant.DebuggerMonitor ..OnEnterBreakMode(EnvDTE.dbgEventReason, EnvDTE.dbgExecutionAction ByRef)+0xab 0012dac0 79e88f63 EnvDTE_ni!EnvDTE._dispDebuggerEvents_SinkHelper.OnEnterBreakMode(EnvDTE.dbgE ventReason, EnvDTE.dbgExecutionAction ByRef)+0x18 0012dac0 79e88ee4 mscorwks!CallDescrWorker+0x33 0012db40 79e88e31 mscorwks!CallDescrWorkerWithHandler+0xa3 0012dc90 79e88d19 mscorwks!MethodDesc::CallDescr+0x19c 0012dca8 79e88cf6 mscorwks!MethodDesc::CallTargetWorker+0x20 0012dcbc 7a11ae16 mscorwks!MethodDescCallSite::Call_RetArgSlot+0x18 0012deb8 7a11b0fa mscorwks!InvokeImpl+0x43f 0012df78 793cf629 mscorwks!RuntimeMethodHandle::InvokeMethodFast+0xbd 01b311ec 794012bf mscorlib_ni!System.RuntimeMethodHandle.InvokeMethodFast(System.Object, System.Object[], System.Signature, System.Reflection.MethodAttributes, System.RuntimeTypeHandle)+0x49 0012dffc 7940114a mscorlib_ni!System.Reflection.RuntimeMethodInfo.Invoke(System.Object, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object[], System.Globalization.CultureInfo, Boolean)+0x167 0012e040 79e88f63 mscorlib_ni!System.Reflection.RuntimeMethodInfo.Invoke(System.Object, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object[], System.Globalization.CultureInfo)+0x1e 0012e040 79e88ee4 mscorwks!CallDescrWorker+0x33 0012e0c0 79e88e31 mscorwks!CallDescrWorkerWithHandler+0xa3 0012e210 79e88d19 mscorwks!MethodDesc::CallDescr+0x19c 0012e228 7a03f495 mscorwks!MethodDesc::CallTargetWorker+0x20 0012ec30 7a03f7a6 mscorwks!DispatchInfo::InvokeMemberWorker+0x893 0012eca4 7a040461 mscorwks!DispatchInfo::InvokeMemberDebuggerWrapper+0x8b 0012ee10 79fd1869 mscorwks!DispatchInfo::InvokeMember+0x2a1 0012eebc 7a02e748 mscorwks!InternalDispatchImpl_Invoke+0x14d 0012eeec 7a02e88a mscorwks!InternalDispatchImpl_Invoke_CallBack+0x3a 0012ef88 54c2899b mscorwks!InternalDispatchImpl_Invoke_Wrapper+0x20a 0012eff4 54bf6fbd vsdebug!CProxy_dispDebuggerEvents<CCPContainerForDebuggerAutomation>::Fire_O nEnterBreakMode+0x104 0012f008 54bab8e4 vsdebug!CDebugger::FireAutomationModeChangeEvent+0x75 0012f024 54bab53a vsdebug!CDebugger::AutomationModeChange+0x33 0012f034 54bab66f vsdebug!CDebugger::OnModeChange+0xaf 0012f0b0 54bb7860 vsdebug!CDebugger::SetDebugMode+0x61 0012f0d0 54bb79af vsdebug!CDebugger::OnEnterBreakState+0x180 0012f0f4 54baea59 vsdebug!CDebugger::OnEnterBreakStateForEvent+0x1f 0012f124 54bab03a vsdebug!CDebugger::HandleEvent+0xb2c 0012f154 54baac6a vsdebug!CDebugger::Event+0x56 0012f1fc 77c70f3b vsdebug!sdm::CDebugManager::HandleEvent+0xb3 0012f250 77ce23f7 RPCRT4!Invoke+0x30 0012f650 77ce1a95 RPCRT4!NdrStubCall2+0x299 0012f6a8 77788ec1 RPCRT4!CStdStubBuffer_Invoke+0xc6 0012f6ec 77788e74 ole32!SyncStubInvoke+0x33 0012f734 7769b2b7 ole32!StubInvoke+0xa7 0012f80c 7769b0b5 ole32!CCtxComChnl::ContextInvoke+0xe3 0012f828 7769bd23 ole32!MTAInvoke+0x1a 0012f854 77788da2 ole32!STAInvoke+0x48 0012f888 77788c33 ole32!AppInvoke+0xa3 0012f95c 777890b3 ole32!ComInvokeWithLockAndIPID+0x2c5 0012f984 7769bc9c ole32!ComInvoke+0x9f 0012f998 7769bac0 ole32!ThreadDispatch+0x23 0012f9b0 7739c3b7 ole32!ThreadWndProc+0xfe 0012f9dc 7739c484 USER32!InternalCallWinProc+0x28 0012fa54 7739c73c USER32!UserCallWinProcCheckWow+0x151 0012fabc 7739c778 USER32!DispatchMessageWorker+0x327 0012facc 5008b9a8 USER32!DispatchMessageW+0xf 0012fb04 500cd542 msenv!EnvironmentMsgLoop+0x294 0012fb18 500cd4e9 msenv!CMsoCMHandler::FPushMessageLoop+0x1f 0012fb40 500cd487 msenv!SCM::FPushMessageLoop+0xb2 0012fb58 500cd458 msenv!SCM_MsoCompMgr::FPushMessageLoop+0x27 0012fb74 500cd3c2 msenv!CMsoComponent::PushMsgLoop+0x25
Jeff, I feel bad to have put you through all of this. It seems that one of
the projects in my solution had the advance compiler option of enable optimizations checked in the debug mode. Having unchecked that box, the issue seems to be resolved. Hope you feel better soon. -- John [quoted text, click to view] ""Jeffrey Tan[MSFT]"" wrote:
> Hi John, > > Sorry for letting you wait, I am sick at home for 2 days :-( > > Yes, I have received your sample project in mailbox. Below is my analysis > process regarding your project: > 1. After unzipping your project, I openned it and tried to debug it by > pressing F5 in VB2005 IDE. Then I got an unhandled exception in the > "Me.Adapter.Fill(dataTable)" in "GetData()" method of DataSet1.Designer.vb > file. Also, the VB2005 IDE will pop up the "Microsoft (R) Visual Basic > Compiler has encountered a problem and needs to close. We are sorry for > the inconvenience." crash dialog. > > By using "Process Explorer", I can see that this dialog(Microsoft > Application Error Reporting process) is actually started by VB2005 IDE > exception handler, see the call stack below: > > msvb7.dll!CreateDWProcess+0xea > msvb7.dll!WatsonFilter+0x4d > msvb7.dll!DoFilterException+0x24 > msvb7.dll!CompilerProject::GetCurrentActiveStatementPosition+0x78 > msvb7.dll!_EH4_CallFilterFunc+0x12 > msvb7.dll!_except_handler4+0x8e > ntdll.dll!ExecuteHandler2+0x26 > ntdll.dll!ExecuteHandler+0x24 > ntdll.dll!KiUserExceptionDispatcher+0xe > > In the details information from the Microsoft Application Error Reporting > dialog, I can find that the unexpected exception is 0xC0000005, which is > Access Violation exception. > > Then, I tried to load windbg to debug this Access Violation in VB2005 IDE. > I got the following full call stack(sorry the call stack is really too > long): > > (2c4.714): Access violation - code c0000005 (first chance) > First chance exceptions are reported before any exception handling. > This exception may be expected and handled. > eax=00000000 ebx=0000000c ecx=0ad2e500 edx=001ba046 esi=12cc0064 > edi=09bf248c > eip=598afb2b esp=0012d6b0 ebp=00000274 iopl=0 nv up ei pl nz na po > nc > cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 > efl=00010202 > msvb7!ENCBuilder::GetCurrentActiveStatementPosition+0x53: > 598afb2b 8b8040020000 mov eax,dword ptr [eax+240h] > ds:0023:00000240=???????? > *** WARNING: Unable to verify checksum for > C:\WINDOWS\assembly\NativeImages_v2.0.50727_32\mscorlib\4fe66c7733005e4fbfe3 > 7c4f11e3cd76\mscorlib.ni.dll > 0:000> kL 50 > ChildEBP RetAddr > 0012d6dc 598afa93 msvb7!ENCBuilder::GetCurrentActiveStatementPosition+0x53 > 0012d71c 5d7335d5 > msvb7!CompilerProject::GetCurrentActiveStatementPosition+0x84 > 0012d734 5d743560 > msvbprj!CVbBldCompiler::GetCurrentActiveStatementPosition+0x44 > 0012d744 54cf6eb8 > msvbprj!CVsProjHierarchy::GetCurrentActiveStatementPosition+0x42 > 0012d7b4 54bb4791 encmgr!CEncMgr::CurrentPositionFromOriginal+0x14c > 0012d84c 54c27e8e vsdebug!CTextPos::SetTextPositionFromDocumentContext+0x156 > 0012d878 79f21268 vsdebug!CDebugger::ShowSource+0x5c > 0012d988 014ea7ca mscorwks!CLRToCOMWorker+0x196 > 0012da04 13f46dc4 CLRStub[StubLinkStub]@14ea7ca > 0012da40 13f4494d > Microsoft_VSDesigner!Microsoft.VSDesigner.ExceptionAssistant.CodeEditorCoope > rator.OpenDocumentWindow(Microsoft.VSDesigner.ExceptionAssistant.ExceptionIn > fo)+0x34 > 0012da90 13f4451b > Microsoft_VSDesigner!Microsoft.VSDesigner.ExceptionAssistant.DebuggerMonitor > .NewAssistantWindow(Microsoft.VSDesigner.ExceptionAssistant.ExceptionInfo, > Boolean)+0x145 > 0012dac0 51a45504 > Microsoft_VSDesigner!Microsoft.VSDesigner.ExceptionAssistant.DebuggerMonitor > .OnEnterBreakMode(EnvDTE.dbgEventReason, EnvDTE.dbgExecutionAction > ByRef)+0xab > 0012dac0 79e88f63 > EnvDTE_ni!EnvDTE._dispDebuggerEvents_SinkHelper.OnEnterBreakMode(EnvDTE.dbgE > ventReason, EnvDTE.dbgExecutionAction ByRef)+0x18 > 0012dac0 79e88ee4 mscorwks!CallDescrWorker+0x33 > 0012db40 79e88e31 mscorwks!CallDescrWorkerWithHandler+0xa3 > 0012dc90 79e88d19 mscorwks!MethodDesc::CallDescr+0x19c > 0012dca8 79e88cf6 mscorwks!MethodDesc::CallTargetWorker+0x20 > 0012dcbc 7a11ae16 mscorwks!MethodDescCallSite::Call_RetArgSlot+0x18 > 0012deb8 7a11b0fa mscorwks!InvokeImpl+0x43f > 0012df78 793cf629 mscorwks!RuntimeMethodHandle::InvokeMethodFast+0xbd > 01b311ec 794012bf > mscorlib_ni!System.RuntimeMethodHandle.InvokeMethodFast(System.Object, > System.Object[], System.Signature, System.Reflection.MethodAttributes, > System.RuntimeTypeHandle)+0x49 > 0012dffc 7940114a > mscorlib_ni!System.Reflection.RuntimeMethodInfo.Invoke(System.Object, > System.Reflection.BindingFlags, System.Reflection.Binder, System.Object[], > System.Globalization.CultureInfo, Boolean)+0x167 > 0012e040 79e88f63 > mscorlib_ni!System.Reflection.RuntimeMethodInfo.Invoke(System.Object, > System.Reflection.BindingFlags, System.Reflection.Binder, System.Object[], > System.Globalization.CultureInfo)+0x1e > 0012e040 79e88ee4 mscorwks!CallDescrWorker+0x33 > 0012e0c0 79e88e31 mscorwks!CallDescrWorkerWithHandler+0xa3 > 0012e210 79e88d19 mscorwks!MethodDesc::CallDescr+0x19c > 0012e228 7a03f495 mscorwks!MethodDesc::CallTargetWorker+0x20 > 0012ec30 7a03f7a6 mscorwks!DispatchInfo::InvokeMemberWorker+0x893 > 0012eca4 7a040461 mscorwks!DispatchInfo::InvokeMemberDebuggerWrapper+0x8b > 0012ee10 79fd1869 mscorwks!DispatchInfo::InvokeMember+0x2a1 > 0012eebc 7a02e748 mscorwks!InternalDispatchImpl_Invoke+0x14d > 0012eeec 7a02e88a mscorwks!InternalDispatchImpl_Invoke_CallBack+0x3a > 0012ef88 54c2899b mscorwks!InternalDispatchImpl_Invoke_Wrapper+0x20a > 0012eff4 54bf6fbd > vsdebug!CProxy_dispDebuggerEvents<CCPContainerForDebuggerAutomation>::Fire_O > nEnterBreakMode+0x104 > 0012f008 54bab8e4 vsdebug!CDebugger::FireAutomationModeChangeEvent+0x75 > 0012f024 54bab53a vsdebug!CDebugger::AutomationModeChange+0x33 > 0012f034 54bab66f vsdebug!CDebugger::OnModeChange+0xaf > 0012f0b0 54bb7860 vsdebug!CDebugger::SetDebugMode+0x61 > 0012f0d0 54bb79af vsdebug!CDebugger::OnEnterBreakState+0x180 > 0012f0f4 54baea59 vsdebug!CDebugger::OnEnterBreakStateForEvent+0x1f > 0012f124 54bab03a vsdebug!CDebugger::HandleEvent+0xb2c > 0012f154 54baac6a vsdebug!CDebugger::Event+0x56 > 0012f1fc 77c70f3b vsdebug!sdm::CDebugManager::HandleEvent+0xb3 > 0012f250 77ce23f7 RPCRT4!Invoke+0x30 > 0012f650 77ce1a95 RPCRT4!NdrStubCall2+0x299 > 0012f6a8 77788ec1 RPCRT4!CStdStubBuffer_Invoke+0xc6 > 0012f6ec 77788e74 ole32!SyncStubInvoke+0x33 > 0012f734 7769b2b7 ole32!StubInvoke+0xa7 > 0012f80c 7769b0b5 ole32!CCtxComChnl::ContextInvoke+0xe3 > 0012f828 7769bd23 ole32!MTAInvoke+0x1a > 0012f854 77788da2 ole32!STAInvoke+0x48 > 0012f888 77788c33 ole32!AppInvoke+0xa3 > 0012f95c 777890b3 ole32!ComInvokeWithLockAndIPID+0x2c5 > 0012f984 7769bc9c ole32!ComInvoke+0x9f
Hi John,
Not at all, it's my job. Thank you for feedback the root cause for the problem. If you need further help, please feel free to post, I will work with you. 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 John.
I am experiencing the same problem too. But in my case, not only one of project will raised error while debugging but all projects do. Before, i assumed that might be caused by a project. so i debugeg some of my finished and release projects. And what?? It raised all the time when you stop, break and event when you start debugging your project. So i try to build very very simple project called "Hello World", (you must know it, don't you?). And then i was trying to stop the debugging, it raised once again. Reinstalling Visual Studio and .Net Framework did not effected anything. I guess VS developers should concern about this. Its not impossible, that someone get fired from his job just because of this thing happened when they are on deadline. -- Best Regards, Nouvanda [quoted text, click to view] "JT" wrote:
> Hi, > I am debugging a project that contains ADO.NET datasets. When I hit a > breakpoint, and press F11 to step into the process, I consistently get a VB > compiler error whenever my debugging takes me into the dataset designer code > file, where the <System.Diagnostics.DebuggerNonUserCode()> attribute lives. > My understanding was that this attribute would cause the debugger to step > through the code, as per these remarks: > > "Designer provided types and members that are not part of the code > specifically created by the user can complicate the debugging experience. > This attribute suppresses the display of these adjunct types and members in > the debugger window and automatically steps through, rather than into, > designer provided code. When the debugger encounters this attribute when > stepping through user code, the user experience is to not see the designer > provided code and to step to the next user-supplied code statement." > > This does not seem to be the case for me. The error is so bad, that I get > prompted to send error reports to Microsoft and have to use task manager to > kill the IDE. Then I have to restart my machine! Is there a way to avoid > this behavior? Thanks. > --
Hi Nouvanda,
I have added a reply to you in your new post regarding this issue, please check it there. I will follow up with you. 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.
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
| home · blog · groups | Questions? Comments? Contact the dn |