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
Motivation
As discussed in https://github.com/falcosecurity/falco/pull/3440/files#r1906703514, the method used to add separate debug symbols (objcopy) won't work on Windows. We should find an appropriate way to do this for Windows environments, but I don't think it should block the current PR.
Different sources have given me different instructions for how to do this with Visual Studio. Possibly with:
Some sources say that Visual Studio generates PDB files automatically with every build and we don't need to do anything. I don't have a test environment set up to work through this right now but I'm sure there's someone out there who does :).
For anyone using Windows but not Visual Studio, it's even less clear to me what the idiomatic way of doing this might be.
Feature
Alternatives
Additional context
The text was updated successfully, but these errors were encountered:
Motivation
As discussed in https://github.com/falcosecurity/falco/pull/3440/files#r1906703514, the method used to add separate debug symbols (objcopy) won't work on Windows. We should find an appropriate way to do this for Windows environments, but I don't think it should block the current PR.
Different sources have given me different instructions for how to do this with Visual Studio. Possibly with:
Or this page suggests this:
Some sources say that Visual Studio generates PDB files automatically with every build and we don't need to do anything. I don't have a test environment set up to work through this right now but I'm sure there's someone out there who does :).
For anyone using Windows but not Visual Studio, it's even less clear to me what the idiomatic way of doing this might be.
Feature
Alternatives
Additional context
The text was updated successfully, but these errors were encountered: