RE: There is no source code available for the current location.
From: Eric Scouten (anonymous_at_discussions.microsoft.com)
Date: 05/26/04
- Next message: Mathias: "RE: There is no source code available for the current location."
- Previous message: Nick: "RE: name space "Microsoft.WindowsCE.Form" is not found"
- In reply to: Robert Gruen [MSFT]: "RE: There is no source code available for the current location."
- Next in thread: Mathias: "RE: There is no source code available for the current location."
- Reply: Mathias: "RE: There is no source code available for the current location."
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 26 May 2004 13:16:03 -0700
I'm having a similar problem. I've verified all of the items that Robert wrote about and found them to be correct. Some specifics about my situation:
1. This is a C# application, using a Managed C++ DLL, which sometimes calls a C# DLL.
2. The problem occurs when the Managed C++ calls a function pointer. (Yes, not a delegate -- function pointers are required because we are also compiling for MacOS in this DLL.)
I am unable to step into or hit any breakpoint in the function pointed to by the function pointer -- or ANY function that it calls. Instead of stopping where I would expect, I get stopped in mscorwks.dll with the "There is no source code available for the current location" message. One level *up* on the stack trace is the function where I would have expected to stop, with the green arrow pointing to the correct line and all local variables displaying as corrected.
What's going on? Is there any workaround?
-Eric
----- Robert Gruen [MSFT] wrote: -----
It sounds like the symbols you have are not lining up with the binaries
you're generating. Do the following:
1. Verify that you are in debug mode and not release mode.
2. Verify that the timestamp of the .pdb file is the same as the .dll or
.exe that you're generating. If they are not, remove all of the binaries
and recompile your entire solution.
3. If the additional assemblies you are trying to debug are not part of
your solution (i.e. other projects), go under the properties for the
solution and be sure to include the "Debug Source Files" and "Debug
Symbol Files" locations of the additional assemblies you're trying to debug.
Thanks! Robert Gruen
Microsoft, VB.NET
This posting is provided "AS IS", with no warranties, and confers no rights.
--------------------
#From: "Peter Afonin" <pafo@specialtypulltabs.com>
#Subject: There is no source code available for the current location.
#Date: Wed, 19 May 2004 16:44:28 -0700
#Lines: 15
#X-Priority: 3
#X-MSMail-Priority: Normal
#X-Newsreader: Microsoft Outlook Express 6.00.3790.0
#X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.132
#Message-ID: <e2BrDufPEHA.2924@TK2MSFTNGP10.phx.gbl>
#Newsgroups: microsoft.public.vsnet.debugging
#NNTP-Posting-Host: 206-124-146-196.blarg.net 206.124.146.196
#Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA06.phx.gbl!TK2MSFTNGXA05.phx.gbl!TK2MSFTNGP0
8.phx.gbl!TK2MSFTNGP10.phx.gbl
#Xref: cpmsftngxa10.phx.gbl microsoft.public.vsnet.debugging:5696
#X-Tomcat-NG: microsoft.public.vsnet.debugging
#
#Hello:
#
#I was always getting sometimes this error while debugging ASP.Net project
in
#VS.Net 2003: "There is no source code available for the current location.",
#but recently I started getting it so often that I almost cannot debug at
#all. What could cause this? Is there a way to fix the situation?
#
#I would appreciate your help.
#
#Thank you,
#
#--
#Peter Afonin
#
#
#
- Next message: Mathias: "RE: There is no source code available for the current location."
- Previous message: Nick: "RE: name space "Microsoft.WindowsCE.Form" is not found"
- In reply to: Robert Gruen [MSFT]: "RE: There is no source code available for the current location."
- Next in thread: Mathias: "RE: There is no source code available for the current location."
- Reply: Mathias: "RE: There is no source code available for the current location."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|