-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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
Build and pack symbols for libuv #2898
Comments
Are we going to include the symbols in the main nuget package or on a myget symbol server? The last time we discussed this, I was told we were saving the old symbols so we could upload them to a symbol server retroactively. |
Apparently we produce these in the libuv-build-windows builds, e.g. $DROPSHARE\libuv-build-windows\dev\10077\build\symbols. We should package these into symbols nupkgs and publish these along with our other symbols. |
@JunTaoLuo did we ever look at this? |
Nope we never triaged this. cc @muratg |
Should this bug go to one of our libuv repos? |
Yes, and we should do this the next time we build libuv |
This issue was moved to aspnet/libuv-build#35 |
The libuv packages we build do not have any corresponding debug symbols. We should explore how we can produce and pack debug symbols in a libuv symbols package and publish this to the symbols server.
cc @davidfowl @halter73 for libuv expertise
cc @Eilon @muratg for triage
cc @natemcmaster for including additional symbols packages in our build.
The text was updated successfully, but these errors were encountered: