You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 73.13%. Comparing base (9705ec2) to head (302f257). ⚠️ Report is 988 commits behind head on main.
gleocadie
changed the title
Gleocadie/add crashtracking feature for windows
Add crashtracking feature for windows (event it's not ready yet)
Sep 6, 2024
gleocadie
changed the title
Add crashtracking feature for windows (event it's not ready yet)
[Profiling/Build] Add crashtracking feature for windows (event it's not ready yet)
Sep 10, 2024
The reason will be displayed to describe this comment to others. Learn more.
It's hard for most of us to try this out without access to a windows machine, but on the other hand the change does look reasonable + it has a really tiny blast radius, so I see no reason not to merge it :)
The reason will be displayed to describe this comment to others. Learn more.
To be honest I do not know. But I observed FFI steps failing: symbolizer could not run because libdatadog_profiling_ffi.so was missing (there is no libdatadog_profiling_ffi.so anymore, it's renamed into libdatadog_profiling.so
When I added this line, the issue went away. (mainly for the ubuntu-latest ones)
It's hard for most of us to try this out without access to a windows machine, but on the other hand the change does look reasonable + it has a really tiny blast radius, so I see no reason not to merge it :)
The package is run on every PR in Gitlab. At least, if files were missing or the names have changed, it would have failed.
But yeah, in my case, I downloaded the nuget package, updated the project with it and built the project.
I plan to add tests:
one on the exported symbols
one on "if the package is correct and be used in a vcxproj (C++ project with Visual Studio)"
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Since #551, crashtracker has its own header
crashtracker.h. This header is not part of the nuget package and prevent compilation on windows.Motivation
Make sure we can compile in Visual Studio.
Additional Notes
Waiting for #611
Anything else we should know when reviewing?
How to test the change?
Downloaded the nuget package (from the gitlab job) and checked that :
crashtracker.his presentddog_crasht_demanglesymbol is present