RE: Re-Re-Repost: Cannot debug Classic ASP with VS2008+SP1
- From: hongyes@xxxxxxxxxxxxxxxxxxxx ("Hongye Sun [MSFT]")
- Date: Mon, 16 Mar 2009 15:46:34 GMT
Hi,
Thanks for your post. I am Hongye Sun from Microsoft Newsgroup Support team
and it is my pleasure to work with you on this issue.
In order to make sure that I does not miss anything in your issue, can you
confirm with me if my understanding is correct?
The problem is that VS 2008 with SP1 crashes with an internal error when
stoping a debug session of classic ASP application. You attach to the
w3wp.exe process with "Script Code" debugger.
If it is correct, the symptom you described is very likely to be a known
issue of VS 2008 SP1. In order to confirm it, can you help us to collect
the call stack information when VS crashes?
Please follow the steps below:
1. Download and install Windbg at link:
http://www.microsoft.com/whdc/devtools/debugging/default.mspx
2. Set the following path in the windbg menu item File->"Symbol File
Path...":
"srv*DownstreamStore*http://msdl.microsoft.com/download/symbols";
Replace DownstreamStore as disk path. for example:
"srv*C:\symbols*http://msdl.microsoft.com/download/symbols";
3. Open the windbg and click File->¡±Open Executable¡¡± and select
devenv.exe, which is located at:
"C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe"
4. Press "F5" or input "g" command to tell windbg to ignore the initial
loader breakpoint.
5. Reproduce the crash in VS.
6. When the application crashes with exception, windbg will automatically
break-in your application. Then you can input "k" command to get the full
stack trace of this exception/failure.
Note: the "k" command may require some time to load the symbols from
Microsoft symbol server for the system dlls the first time. So the windbg
will report "busy..." for sometime. You may wait to have a coffee for the
symbol loading and output.
For more information about using Windbg to obtain applicaiton crash
information, please visit following website:
http://blogs.msdn.com/msdnts/archive/2006/11/24/how-to-debug-application-cra
sh-hang-in-production-environment.aspx
Before we can confirm that the issue is a known bug, can you do the
following actions to exclude the possibilities of third party add-in or
environment issues.
1. Open up Visual Studio command prompt
2. Run the following command
devenv /SafeMode
3. Once Visual Studio opens up, open your website and then debug it, let me
know if the crash occurs
Once you have completed the above test try the following
1. Open up Visual Studio command prompt
2. Run the following commands and close the Visual Studio every time it
opens up
devenv /ResetSkipPkgs
devenv /ResetAddin
3. Open Visual Studio and then debug your website and check if you are able
to reproduce the issue
Please Note: When you are running ResetAddin Visual Studio will remove any
command's OR command UI associated with the AddIn's.
Thanks for your cooperation to collect all the informaiton above.
In addition, I understand that you experienced a no-spam alias issue. I am
sorry for any inconvinience to you. If you have similiar issues again in
future, please contact us via this email: msdnmg@xxxxxxxxxxxxxx We will
support you as soon as possible and forward your issue to proper channel.
Have a nice day.
Regards,
Hongye Sun (hongyes@xxxxxxxxxxxxxxxxxxxx, remove 'online.')
Microsoft Online Community Support
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@xxxxxxxxxxxxxx
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/en-us/subscriptions/aa948868.aspx#notifications.
Note: MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within?2 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. 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/en-us/subscriptions/aa948874.aspx
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
.
- Follow-Ups:
- RE: Re-Re-Repost: Cannot debug Classic ASP with VS2008+SP1
- From: mynewpostingalias-again
- RE: Re-Re-Repost: Cannot debug Classic ASP with VS2008+SP1
- References:
- Re-Re-Repost: Cannot debug Classic ASP with VS2008+SP1
- From: mynewpostingalias-again
- Re-Re-Repost: Cannot debug Classic ASP with VS2008+SP1
- Prev by Date: Need help with debugging minidumps in VS2008
- Next by Date: Facts and Statistics about bugs, debug techniques etc
- Previous by thread: Re-Re-Repost: Cannot debug Classic ASP with VS2008+SP1
- Next by thread: RE: Re-Re-Repost: Cannot debug Classic ASP with VS2008+SP1
- Index(es):
Relevant Pages
|
Loading
