[GH-ISSUE #44] Debug directory removed from PE header #37

Closed
opened 2026-02-25 21:30:31 +03:00 by kerem · 2 comments
Owner

Originally created by @Sam13 on GitHub (May 16, 2018).
Original GitHub issue: https://github.com/brutaldev/StrongNameSigner/issues/44

By comparing the PE header of an existing unsigned assembly and the same assembly signed with StrongNameSigner, I found out that the "Debug directory" is stripped out from the PE header.

Without information in the header that it's e.g. impossible to generate a PDB with JetBrains dotPeek (https://youtrack.jetbrains.com/issue/DOTP-6889)

I'm using version 2.1.4

Originally created by @Sam13 on GitHub (May 16, 2018). Original GitHub issue: https://github.com/brutaldev/StrongNameSigner/issues/44 By comparing the PE header of an existing unsigned assembly and the same assembly signed with StrongNameSigner, I found out that the "Debug directory" is stripped out from the PE header. Without information in the header that it's e.g. impossible to generate a PDB with JetBrains dotPeek (https://youtrack.jetbrains.com/issue/DOTP-6889) I'm using version 2.1.4
kerem closed this issue 2026-02-25 21:30:31 +03:00
Author
Owner

@brutaldev commented on GitHub (Nov 2, 2021):

@Sam13 I've tested this myself and the directory is not stripped at all. Do you have an assembly with corresponding PDB that this happens with? I used tools like PE Editor to verify the header.

<!-- gh-comment-id:957281762 --> @brutaldev commented on GitHub (Nov 2, 2021): @Sam13 I've tested this myself and the directory is not stripped at all. Do you have an assembly with corresponding PDB that this happens with? I used tools like [PE Editor](https://github.com/petoolse/petools) to verify the header.
Author
Owner

@Sam13 commented on GitHub (Nov 14, 2021):

@brutaldev I'm afraid, I cannot provide any test data. Since you tested again I would consider this fixed...

<!-- gh-comment-id:968326320 --> @Sam13 commented on GitHub (Nov 14, 2021): @brutaldev I'm afraid, I cannot provide any test data. Since you tested again I would consider this fixed...
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/StrongNameSigner#37
No description provided.