Skip to content

Mark object type exports as DATA#303

Merged
kumarvin123 merged 1 commit intomainfrom
fix-object-type-data-exports
May 5, 2026
Merged

Mark object type exports as DATA#303
kumarvin123 merged 1 commit intomainfrom
fix-object-type-data-exports

Conversation

@Alan-Jowett
Copy link
Copy Markdown
Member

Summary

Mark ExEventObjectType and IoFileObjectType as DATA exports in src/Source.def.

Why

These are exported globals, but the .def file listed them as plain exports. When an ARM64 import library is generated from that file, both symbols are emitted as Type: code instead of Type: data.

That mismatches how ebpf-for-windows consumes the symbols and can trigger ARM64 link failures such as the LNK2048 / LNK1165 relocation errors seen in the usersim-backed NativeOnlyDebug build.

Validation

Generating an ARM64 import library from the updated Source.def changes both symbols to Type: data.

Ensure ExEventObjectType and IoFileObjectType are emitted as data imports in the ARM64 usersim import library.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@Alan-Jowett Alan-Jowett requested a review from mtfriesen as a code owner May 5, 2026 21:47
@kumarvin123 kumarvin123 merged commit c06cb9f into main May 5, 2026
12 checks passed
@kumarvin123 kumarvin123 deleted the fix-object-type-data-exports branch May 5, 2026 21:59
kumarvin123 pushed a commit that referenced this pull request May 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants