The debug directory payload is not located directly after the debug directory entry itself, but can essentially be located anywhere in the binary (even outside of mapped sections, although we don't handle that case).
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
llvm/test/tools/llvm-objcopy/COFF/debug-dir-unmapped.test | ||
---|---|---|
4 | nit:
i'd use the default one (CHECK) |
llvm/test/tools/llvm-objcopy/COFF/debug-dir-unmapped.test | ||
---|---|---|
4 | Fair enough, I'll change that before pushing. |
llvm/test/tools/llvm-objcopy/COFF/debug-dir-unmapped.test | ||
---|---|---|
2 | Could you add a top-level comment to this and the other test saying exactly what this is testing, and how it is testing it (if not obvious from the "what"), please? | |
llvm/tools/llvm-objcopy/COFF/Writer.cpp | ||
386 | Are COFF addresses limited to 32-bits? Or should this really be a 64-bit value? | |
llvm/tools/llvm-objcopy/COFF/Writer.h | ||
48 | I think RVA is more correct for acronyms. Same applies in the .cpp. |
llvm/test/tools/llvm-objcopy/COFF/debug-dir-unmapped.test | ||
---|---|---|
2 | Sure, will do. | |
llvm/tools/llvm-objcopy/COFF/Writer.cpp | ||
386 | PECOFF images are essentially limited to 32 bit in size, yes. And the PointerToRawData field that this is going to be stored in in the end is support::ulittle32_t anyway. | |
llvm/tools/llvm-objcopy/COFF/Writer.h | ||
48 | Right, will change. |
Added comments to the testcases, changed -R into --remove-section in the tests, changed the variable name Rva into RVA.
llvm/test/tools/llvm-objcopy/COFF/debug-dir-unmapped.test | ||
---|---|---|
2–4 | Thanks, will fix before pushing. |
Could you add a top-level comment to this and the other test saying exactly what this is testing, and how it is testing it (if not obvious from the "what"), please?