Fixing a small typo.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Fix the error message to check for the exact error message and this is good to go.
lldb/test/Shell/SymbolFile/DWARF/range-lower-then-low-pc.s | ||
---|---|---|
11 | might be good to verify that the correct DIE offset of the block ID is. in the error message. If this code hadn't assert'ed we still might have gotten a string output, but we need to verify the data is correct. If you run it manually once you can see the exact error message we will need to check for. |
lldb/test/Shell/SymbolFile/DWARF/range-lower-then-low-pc.s | ||
---|---|---|
12 | Shouldn't the low PC of the function be zero? |
FYI: This might be because we are using a .o file and relocations are being applied internally!?
lldb/test/Shell/SymbolFile/DWARF/range-lower-then-low-pc.s | ||
---|---|---|
12 | 0x00000043: DW_TAG_subprogram DW_AT_low_pc (0x0000000000000001) DW_AT_high_pc (0x000000000000002e) DW_AT_frame_base (DW_OP_reg6 RBP) DW_AT_linkage_name ("_ZL3foob") DW_AT_name ("foo") DW_AT_decl_file ("base-lower-then-range-entry/base-lower-then-range-entry/main.cpp") DW_AT_decl_line (1) DW_AT_type (0x0000008b) 0x00000060: DW_TAG_formal_parameter DW_AT_location (DW_OP_fbreg -5) DW_AT_name ("b") DW_AT_decl_file ("base-lower-then-range-entry/base-lower-then-range-entry/main.cpp") DW_AT_decl_line (1) DW_AT_type (0x00000092) 0x0000006e: DW_TAG_lexical_block DW_AT_ranges (0x00000000 [0x0000000000000000, 0x000000000000001f) [0x0000000000000000, 0x000000000000002d)) Seems like we have a bug in the code that prints the error message? |
lldb/test/Shell/SymbolFile/DWARF/range-lower-then-low-pc.s | ||
---|---|---|
12 | Stepped through the code 0x21 is what gets extracted in DWARFDebugInfoEntry::GetDIENamesAndRanges. |
Looked through llvm-dwarfdump code. Yep. since relocation exists, it just returns an addend which is 1.
might be good to verify that the correct DIE offset of the block ID is. in the error message. If this code hadn't assert'ed we still might have gotten a string output, but we need to verify the data is correct. If you run it manually once you can see the exact error message we will need to check for.