Re: There is no source code available for the current location
From: jlconley (jlconley_at_discussions.microsoft.com)
Date: 12/07/04
- Next message: Kevin D: "Cannot attach debugger to a running service built with VS 6.0"
- Previous message: Claudio Pacciarini: "RE: Non-Admin, ASP.NET, debug problem."
- In reply to: snewman: "Re: There is no source code available for the current location"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 7 Dec 2004 12:42:14 -0800
I have seen it in both versions of .net. It is very annoying and I a fix was
available. I have found a work around for it though. Start your application
without debugging, then attach to the process. This is the same way you
would debug a service.
"snewman" wrote:
> Does anyone know what the underlying issue is? I am experiencing a similar
> problem: I'm running a Windows Forms application under the VS.NET debugger.
> The application has a menu item which runs a bunch of unit tests. I have the
> debugger set to trap on all exceptions (handled or otherwise). Quite often,
> if the unit test trips an exception and I drop into the debugger, it gives
> the "There is no source code available for the current location" message. On
> these occasions, breakpoints also don't seem to work (i.e. if I had placed a
> breakpoint prior to the error, it doesn't trip). The behavior is
> intermittent for me -- half the time everything is fine, other times I get
> this problem.
>
> It seems likely that I'm experiencing the same underlying bug, but I'm
> coming at it from a different direction, so I'm not sure what workaround to
> use. The bulk of my code is NOT running in a timer event. I do make some
> use of timers, but when I get the "no source code available" message, I'm
> usually not in a timer event. So I'm not sure how to apply the workarounds
> described in this posting or the KB article.
>
> So... does anyone know what the actual VS.NET bug is, or a more general
> workaround for it?
>
> One last note: the code I'm testing spawns a number of background threads,
> and sometimes calls Thread.Sleep. I don't know whether this might be a
> factor. Most of the interesting code is running in the main thread, and
> that's where I see the problem.
>
> -- Steve
- Next message: Kevin D: "Cannot attach debugger to a running service built with VS 6.0"
- Previous message: Claudio Pacciarini: "RE: Non-Admin, ASP.NET, debug problem."
- In reply to: snewman: "Re: There is no source code available for the current location"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|