Re: Debug and break point problem - There is no source code available

Thanks for the reply Paul

glad to know I'm not alone

I suppose the next step is to recreate the project on the other machine,
manually recreate all the classes and then paste the code in... what a
nightmare!!!

if I find anything else out I'll le you know.

cheers

Andy

"Paul" <Paul@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0DDFD92E-1E20-4483-9329-3A65EEA7674F@xxxxxxxxxxxxxxxx
> I've all of a sudden encountered the "no source code" errors as well and
> nothing really changed in my apps. Just all of a sudden they stopped
> allowing me to debug them?! I, too, moved the source code from one
> location
> to another (my C: to the corporate network) but that was quite a while ago
> and I'm fairly certain I've debugged successfully since then.
>
> I started a new project and confirmed that I can debug it.
> I've moved the source BACK to my C drive and still cannot debug.
>
> Keep me posted on this and I'll let you know if I learn anything.
> Paul
>
> "aaj" wrote:
>
>> Hi all
>>
>> I have written a small app on my machine that I have passed on to a
>> colleague for testing.
>>
>> The problem is, as soon as he steps through in debug mode and reaches
>>
>> try
>> {
>> conn.Open(); <- HERE
>>
>> The error message 'There is no source code available for the current
>> location ' pops up. I should stress this is not a caught error, but one
>> the
>> IDE generates.
>>
>> It can be temporarily fixed by us logging off, logging on and then
>> rebuilding the solution. It only works for one pass, and then the second
>> time you step through the error re appears.
>>
>> I have searched Google and found a few references to the same problem,
>> but
>> no fixes. Microsoft knowledge base 318367 suggests a fix, but didn't
>> work.
>>
>> There are two things I can see
>>
>> 1) I run .net framework 1.1.4322 while he has the same number but has
>> installed sp1
>>
>> 2) the other is the project originally lived on my D drive, but its on
>> his
>> C. .NET took care of most of the paths, but as suggested in article
>> 318367,
>> I had to manually change the reference in the Solution properties. Doing
>> this fixed the problem for a single execution, but fails at the second
>> attempt.
>>
>> one last thing, if we run in 'Release' everything runs fine
>>
>> any help would be much appreciated
>>
>> thanks
>>
>> Andy
>>
>>
>>


.

Relevant Pages

  • Re: Debug and break point problem - There is no source code availa
    ... I, too, moved the source code from one ... >> I started a new project and confirmed that I can debug it. ... >>> It can be temporarily fixed by us logging off, ... >>> I had to manually change the reference in the Solution properties. ...
    (microsoft.public.dotnet.general)
  • Re: Unable to DEbug the Driver in the user mode
    ... I have Printer driver code which uses uniDrv & OEMUI code. ... ANOTHER INTEROP dLL WHICH TRANSFER THE BYTE ARRAY TO .nET ... I am getting some information about the debug content ... but I am not able to debug source code line by line. ...
    (microsoft.public.development.device.drivers)
  • Re: debugging in release mode
    ... The idea that source code was in the .exe was my misconception. ... The alert is a callback. ... SInce I now know that it is not giving away any secrets to deliver debug ... and then turn off optimizations and turn on generation of debug ...
    (microsoft.public.vc.mfc)
  • Re: Seg fault even though address space is accessible
    ... There's a guy around here somewhere who can debug your problem (no ... matter what it is) using only the debugger. ... debugger and not seeing the source code. ... I did extend the position held by one of the trolls that the debugger ...
    (comp.lang.c)
  • Re: Big problems with glibc - how to debug?
    ... >> kernel services back ported to the Red Hat 2.4 kernels. ... Hat installs. ... this that I can debug with source code;-) ... > have a one-line change in source code which triggers the problem. ...
    (comp.os.linux.development.apps)
Loading