Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
Unable to debug into NuGet package
-
- I've also noticed that for the bad pdb files there is no, 'Microsoft C/C++ MSF 7.00' header at the top
- The bad pdb's also do not contain a section like, 'SRCSRV: source files ---------------------------------------'
- Using the srctool.exe -r on a bad pdb returns no results
- I extracted some of Inedo's code, ran it locally and it was successful. Multiple versions of pdbstr.exe were used successfully.
- Using a locally installed(IIS) version of ProGet was successful.
- The only place I get the failure is with ProGet installed on Windows server 2012(IIS).
-
My ProGet is installed on Server 2008 R2, not Server 2012.
-
Thanks for the detailed debugging; this one is a giant pain to figure out, as you're noticing!
Jim -- can you try running that code you extracted on the Server 2012 that's failing? I'm wondering if pdbstr.exe is silently failing due to missing dependencies, and producing these "bad" pdb files.
-
Steve,
It's probably not the answer you were looking for, but it DOES work if I copy my console application to the 2012 server and run it. If I take the resulting pdb from the console app, I can copy it to my local symbol server and use it to step into the code. It correctly contacts the ProGet server and downloads the source. Also, my code uses the same pdbstr.exe that ProGet does(C:\Windows\Temp\inedopgsrcsrv\pdbstr.exe).
As noted above the bad pdb is smaller in size(KB) to the correctly generated pdb.
-
Thanks Jim; exactly what I was wondering.
Can you by chance send this console app and src to support - at - inedo . com? This could probably help debug this too.
-
I was able to reproduce the bad pdb in terms of exact byte size, by writing the stream out before the call to GetIndexedPdb is made. My guess is the Process that starts pdbstr is failing silently. Unfortunately nothing is being logged in that case. Is it possible for someone to add some logging? I would be willing to test in my environment.
-
Good news! We're finally able to reproduce this on our end.
It turns out the version of pdbstr.exe we've embedded (from the 2008R2/W7 SDK) has a hidden dependency on some ancient dll (mspdb60.dll). That DLL is installed with the SDK, and in some Visual Studio SKUs, and pdbstr.exe will silently fail if it's not inclused.
We're investigating further, and will ship a maintenance release to address this soon.
-
Just to let everyone know that's been following this thread - ProGet 2.2.12 has been released which should address all of these issues. Thanks to everyone for your help in tracking this down!
-
It's now working!
Thanks.
-
I can also confirm that it's working now. Thanks for the steady support.
-
It's working for us too.
Thanks!
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better đŸ’—
Register Login