llvm-project

Author SHA1 Message Date

Author	SHA1	Message	Date
nerix	44fefe70e4	[LLDB][NativePDB] Estimate symbol sizes (#165727 ) In #165604, a test was skipped on Windows, because the native PDB plugin didn't set sizes on symbols. While the test isn't compiled with debug info, it's linked with `-gdwarf`, causing a PDB to be created on Windows. This PDB will only contain the public symbols (written by the linker) and section information. The symbols themselves don't have a size, however the DIA SDK sets a size for them. It seems like, for these data symbols, the size given from DIA is the distance to the next symbol (or the section end). This PR implements the naive approach for the native plugin. The main difference is in function/code symbols. There, DIA searches for a corresponding `S_GPROC32` which have a "code size" that is sometimes slightly smaller than the difference to the next symbol.	2025-10-31 10:33:37 +01:00
Alex Langford	dbffd0aeaf	[lldb] Add lld requirement to NativePDB test (#161731 ) The cpp file fails to build without `lld-link`.	2025-10-02 13:50:11 -07:00
nerix	65787728b7	[LLDB][NativePDB] Implement `AddSymbols` (#154121 ) This PR implements `SymbolFileNativePDB::AddSymbols` which adds public symbols to the symbol table. These symbols are found in the publics stream. It contains mangled names coupled with addresses. Addresses are a pair of (segment, offset). If I understood correctly, then the segment is the section ID from the COFF header. Sections are already [constructed](`c48ec7fb60/lldb/source/Plugins/ObjectFile/PECOFF/ObjectFilePECOFF.cpp (L1048)`) using this 1-based index ([MS docs](https://learn.microsoft.com/en-us/windows/win32/debug/pe-format#section-table-section-headers)). This allows us to use `section_list->FindSectionByID`.	2025-09-11 22:35:19 +02:00

nerix

44fefe70e4

[LLDB][NativePDB] Estimate symbol sizes (#165727 )

In #165604, a test was skipped on Windows, because the native PDB plugin
didn't set sizes on symbols. While the test isn't compiled with debug
info, it's linked with `-gdwarf`, causing a PDB to be created on
Windows. This PDB will only contain the public symbols (written by the
linker) and section information. The symbols themselves don't have a
size, however the DIA SDK sets a size for them.
It seems like, for these data symbols, the size given from DIA is the
distance to the next symbol (or the section end).

This PR implements the naive approach for the native plugin. The main
difference is in function/code symbols. There, DIA searches for a
corresponding `S_GPROC32` which have a "code size" that is sometimes
slightly smaller than the difference to the next symbol.

2025-10-31 10:33:37 +01:00

Alex Langford

dbffd0aeaf

[lldb] Add lld requirement to NativePDB test (#161731 )

The cpp file fails to build without `lld-link`.

2025-10-02 13:50:11 -07:00

nerix

65787728b7

[LLDB][NativePDB] Implement AddSymbols (#154121 )

This PR implements `SymbolFileNativePDB::AddSymbols` which adds public
symbols to the symbol table.

These symbols are found in the publics stream. It contains mangled names
coupled with addresses. Addresses are a pair of (segment, offset).
If I understood correctly, then the segment is the section ID from the
COFF header. Sections are already
[constructed](c48ec7fb60/lldb/source/Plugins/ObjectFile/PECOFF/ObjectFilePECOFF.cpp (L1048))
using this 1-based index ([MS
docs](https://learn.microsoft.com/en-us/windows/win32/debug/pe-format#section-table-section-headers)).
This allows us to use `section_list->FindSectionByID`.

2025-09-11 22:35:19 +02:00

3 Commits