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
Linux has pahole but we don't yet have an equivalent tool for eBPF for Windows.
Such a tool would read a .pdb file and generate BTF data to be added to an ELF file. Bing copilot explains:
The pahole tool is part of the DWARF project and is used in the context of BPF (Berkeley Packet Filter) to generate BTF (BPF Type Format) information from non-stripped ELF files that contain DWARF debug data. Here's a brief overview of what it does:
Input: pahole takes an ELF file as input, which can be either the kernel or a standard eBPF ELF object.
Processing: It processes the DWARF debug data within the ELF file to extract type information.
Output: The tool appends two additional ELF sections with BTF encoding to the input ELF file. This BTF information can then be used by BPF tools to provide better type information and improve debugging and profiling[1].
For Windows, the input would be the PDB file but otherwise would work similarly.
BTF info in the ELF file would allow calling helpers by BTF ID instead of by static ID, thus solving the problem of coordinating static IDs across extensions including third party extensions.
In the future it might (needs investigation) even be possible to have a BTF ID for a prog type and/or attach type, to avoid having to coordinate those as well.
Proposed solution
Create a tool for windows.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the feature you'd like supported
Linux has pahole but we don't yet have an equivalent tool for eBPF for Windows.
Such a tool would read a .pdb file and generate BTF data to be added to an ELF file. Bing copilot explains:
For Windows, the input would be the PDB file but otherwise would work similarly.
BTF info in the ELF file would allow calling helpers by BTF ID instead of by static ID, thus solving the problem of coordinating static IDs across extensions including third party extensions.
In the future it might (needs investigation) even be possible to have a BTF ID for a prog type and/or attach type, to avoid having to coordinate those as well.
Proposed solution
Create a tool for windows.
Additional context
No response
The text was updated successfully, but these errors were encountered: