Repository navigation
Cannot debug VFT inself anymore - FSharp.Editor has no PDB file #2771
Description
- git cleanup
- deleted
c:\Users\me\AppData\Local\Microsoft\VisualStudio\15.0_183b437fFSharpDev - deleted
c:\Users\me\AppData\Roaming\Microsoft\VisualStudio\15.0_183b437fFSharpDev build vs- build VFT solution inside VS
- Ctrl+F5
- attached to the exp instance
- tried to set a breakpoint in several places in FSharp.Editor and FSharp.Language.Service
Activity
forki commentedon Apr 2, 2017
vasily-kirichenko commentedon Apr 2, 2017
wow :((
forki commentedon Apr 2, 2017
vasily-kirichenko commentedon Apr 2, 2017
I think the big diff was switching to more nuget VS packages instead of GAC deps.
forki commentedon Apr 2, 2017
Sigh.
I think @cloudRoutine said something about nuget packages messing up his editor support yesterday. Why is this shit never working?
OK so what now? Can you reset before that and confirm it broke us?
vasily-kirichenko commentedon Apr 2, 2017
vasily-kirichenko commentedon Apr 2, 2017
I'm completely stuck on working on VFT at the moment :(
cloudRoutine commentedon Apr 2, 2017
tried adding
to
visualfsharpopensource.csproj, only seemed to make symbols load fasterafter disabling just my code in debug settings
Changing the setting suggested in the image below made no difference
cloudRoutine commentedon Apr 2, 2017
After trying to set a breakpoint crashed VS
I was able to set some breakpoints that came up as invalid while loading the experimental instance once it was actually running
vasily-kirichenko commentedon Apr 2, 2017
I looked at what FSharp.Editor.dll is actually loaded and there no *.pdb in that folder at all:
vasily-kirichenko commentedon Apr 2, 2017
I've copied *.pdb manually, it's not helped.
vasily-kirichenko commentedon Apr 2, 2017
'devenv.exe' (CLR v4.0.30319: DefaultDomain): Loaded 'C:\USERS\VASKI\APPDATA\LOCAL\MICROSOFT\VISUALSTUDIO\15.0_183B437FFSHARPDEV\EXTENSIONS\MICROSOFT.VISUALFSHARPTOOLS\VISUAL F# TOOLS\42.42.42.42\FSharp.Editor.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.Why the hell it's optimized??
sergey-tihon commentedon Apr 2, 2017
not sure if it is related, but after update to latest nightly, VS2017 asked to install some VS updates ...
After installation I cannot open solutions with F# projects and I found that
VFTextension is disablesI can not do anything about it for now...
cartermp commentedon Apr 2, 2017
@sergey-tihon Can you run VSIXInstaller to remove the nightly and load F# projects after that? (It should be using the vs2017 RTW version of the tools).
[-]Cannot debug VFT inself anymore[/-][+]Cannot debug VFT inself anymore - FSharp.Editor has no PDB file[/+]cloudRoutine commentedon Apr 2, 2017
cc @ctaggart
cloudRoutine commentedon Apr 2, 2017
switching back to my
navigable-improvementsbranch/PR and the problem disappearsso the problem should be within
cloudRoutine/fsharp@navigable-improvements...cloudRoutine:master
0x53A commentedon Apr 2, 2017
There seems to be an issue with portable PDBs:
After disabling optimizations and setting DebugType: full, all breakpoints bind, and all except two (the marked lines) also actually hit.
master...0x53A:debuggable
I had to disable sourcelink, because sourcelink only works with portable pdbs.
With optimizations enabled, some breakpoints wouldn't bind, but the ones that bound then also got hit.
majocha commentedon Apr 3, 2017
Thanks @0x53A ! It started to work with your fix, but only after another git clean.
0x53A commentedon Apr 3, 2017
@majocha you don't need to clean, but you need to change anything in any file, because the up-to-date check doesn't check the
FSharpSource.Settings.targets, and so doesn't rebuild by default. I always just added/removed one space in FSharp.Editor when testing this.forki commentedon Apr 3, 2017
clean is often needed if you want to rebuild proto or when nuget fucked up again.
forki commentedon Apr 4, 2017
This is really really painful
majocha commentedon Apr 4, 2017
Yeah, I'm totally blocked again. Breakpoints fail to bind.
cartermp commentedon Apr 4, 2017
cc @KevinRansom @brettfo - this has to be resolved quickly.
vasily-kirichenko commentedon Apr 8, 2017
Fixed in master.