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

Source bundle creation fails on PE with embedded PPDB #1491

Closed
mattjohnsonpint opened this issue Feb 24, 2023 · 4 comments
Closed

Source bundle creation fails on PE with embedded PPDB #1491

mattjohnsonpint opened this issue Feb 24, 2023 · 4 comments

Comments

@mattjohnsonpint
Copy link
Contributor

Sentry CLI 2.13.0 added support for PPDB embedded in the PE assembly with #1463. That's working fine, and will also use the embedded debug info to derive sources when using sentry-cli dif upload --include-sources. However, I can't seem to use an embedded PPDB when trying to separately create a source bundle using sentry-cli dif bundle-sources.

In other words, this works:

dotnet new console -n ConsoleApp1
cd ConsoleApp1
dotnet build
sentry-cli dif bundle-sources obj/Debug/net7.0/ConsoleApp1.pdb

But this doesn't work, and it should:

dotnet new console -n ConsoleApp1
cd ConsoleApp1
dotnet build -p:DebugType=embedded
sentry-cli dif bundle-sources obj/Debug/net7.0/ConsoleApp1.dll

Even though this works:

dotnet new console -n ConsoleApp1
cd ConsoleApp1
dotnet build -p:DebugType=embedded
sentry-cli dif upload obj/Debug/net7.0/ConsoleApp1.dll --include-sources
@mattjohnsonpint
Copy link
Contributor Author

The output when failed is simply:

skipped obj/Debug/net7.0/ConsoleApp1.dll (no files found)

@vaind
Copy link
Collaborator

vaind commented Feb 27, 2023

The difference lies in debug-files upload executing search_difs()->collect_object_dif() which expands the given path to the actually useful file, i.e. ConsoleApp1.pdb. This is because upload-dif is normally used with a directory path, not individual file path.

bundle-sources doesn't do that, it just takes the single given file path and processes it.

Whether these two should behave like that - not sure. There are arguments both ways for each situation...

@github-actions
Copy link

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!


"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

@szokeasaurusrex
Copy link
Member

Closing – per @vaind's comment, this appears to be expected behavior

@szokeasaurusrex szokeasaurusrex closed this as not planned Won't fix, can't repro, duplicate, stale Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants