Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need API to read SourceLink information from Windows PDBs #2519

Closed
JohnTortugo opened this issue Apr 15, 2019 · 11 comments
Closed

Need API to read SourceLink information from Windows PDBs #2519

JohnTortugo opened this issue Apr 15, 2019 · 11 comments

Comments

@JohnTortugo
Copy link
Contributor

Issue originated after discussion on this other issue: dotnet/arcade-services#2467

It's what the title say. We need a tool that can read SourceLink information from Windows PDBs. See messages from @tmat below for better context.

From @JohnTortugo here:

AFAIU right now sourcelink cli tool can only handle Portable PDBs and the PDBs that we have during publish/release are Windows PDBs. I'm still investigating.

From @tmat here:

I don't think we have the necessary APIs in Microsoft.DiaSymReader/Native to read native source link data (they are stored in a different stream within the PDB than managed ones). No problem adding those APIs it's just work.

So I suggest we separate validation of Source Link Portable PDBs and native (C++ generated) PDBs. Let's make sure our Portable PDBs are good first and later on we can add validation of native PDBs.

@jcagme
Copy link
Contributor

jcagme commented Jun 3, 2019

Hey @JohnTortugo what's the latest here? Is this required for your work to be completed by end of June?

@JohnTortugo
Copy link
Contributor Author

This is not a blocker for publishing itself. It's a blocker for how complete our validation process is: currently our source link validation is only performed in Portable PDBs.

I don't think this is a blocker for P6/P7 . @mmitche , @markwilkie for awareness

@jcagme
Copy link
Contributor

jcagme commented Jun 3, 2019

Given that works only on portable PDBs could we safely say that things were validated? What's the risk of not validating Windows only PDBs?

@JohnTortugo
Copy link
Contributor Author

I think the Windows PDB's are mostly from building C++ sources. @tmat can answer that question better.

@tmat
Copy link
Member

tmat commented Jun 3, 2019

The only concern imo is PDBs built by C++.

@riarenas
Copy link
Member

Moving to the ringed releases epic.

@jcagme jcagme changed the title Need API to read SourceLink information from Windows PDBs [QCR][Validation ring] Need API to read SourceLink information from Windows PDBs Mar 12, 2020
@jcagme jcagme added the QuickConfidentReleases Issues related to the "Releases are quick and have high confidence" Epic label Mar 16, 2020
@michellemcdaniel
Copy link
Contributor

Out of scope for #6418.

@michellemcdaniel michellemcdaniel changed the title [QCR][Validation ring] Need API to read SourceLink information from Windows PDBs Need API to read SourceLink information from Windows PDBs Apr 22, 2021
@michellemcdaniel michellemcdaniel removed the QuickConfidentReleases Issues related to the "Releases are quick and have high confidence" Epic label Apr 22, 2021
@jakubstilec
Copy link
Contributor

jakubstilec commented Apr 29, 2021

[Async Triage]: @adiaaida where this should go when it was removed from #6418? When it hasn't been done for 2 years maybe we can close it?

@markwilkie
Copy link
Member

@mmitche - wondering if we should/could close this one too....

@MattGal
Copy link
Member

MattGal commented Apr 29, 2021

[Async Triage]: I favor closing the issue; if someone cares the issue would need to be in https://github.com/dotnet/sourcelink anyways.

@jakubstilec
Copy link
Contributor

[Async Triage]: no objection to close it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants