Skip to content

Conversation

@romainthomas
Copy link
Contributor

In some cases (c.f. the attached binary), getAsSectionOffset() is failing and thus, the inline de-referencing
is wrong.

D_test.bin.zip

@github-actions
Copy link

Thank you for submitting a Pull Request (PR) to the LLVM Project!

This PR will be automatically labeled and the relevant teams will be notified.

If you wish to, you can add reviewers by using the "Reviewers" section on this page.

If this is not working for you, it is probably because you do not have write permissions for the repository. In which case you can instead tag reviewers by name in a comment by using @ followed by their GitHub username.

If you have received no comments on your PR for a week, you can request a review by "ping"ing the PR by adding a comment “Ping”. The common courtesy "ping" rate is once a week. Please remember that you are asking for valuable time from other developers.

If you have further questions, they may be answered by the LLVM GitHub User Guide.

You can also ask questions in a comment on this PR, on the LLVM Discord or on the forums.

@llvmbot
Copy link
Member

llvmbot commented Nov 16, 2024

@llvm/pr-subscribers-debuginfo

Author: Romain Thomas (romainthomas)

Changes

In some cases (c.f. the attached binary), getAsSectionOffset() is failing and thus, the inline de-referencing
is wrong.

D_test.bin.zip


Full diff: https://github.com/llvm/llvm-project/pull/116479.diff

1 Files Affected:

  • (modified) llvm/lib/DebugInfo/DWARF/DWARFDie.cpp (+6-2)
diff --git a/llvm/lib/DebugInfo/DWARF/DWARFDie.cpp b/llvm/lib/DebugInfo/DWARF/DWARFDie.cpp
index c1cd587877de0c..a14e4451d5dba8 100644
--- a/llvm/lib/DebugInfo/DWARF/DWARFDie.cpp
+++ b/llvm/lib/DebugInfo/DWARF/DWARFDie.cpp
@@ -394,9 +394,13 @@ Expected<DWARFAddressRangesVector> DWARFDie::getAddressRanges() const {
 
   std::optional<DWARFFormValue> Value = find(DW_AT_ranges);
   if (Value) {
+    std::optional<uint64_t> SecOff = Value->getAsSectionOffset();
+    if (!SecOff) {
+      return DWARFAddressRangesVector();
+    }
     if (Value->getForm() == DW_FORM_rnglistx)
-      return U->findRnglistFromIndex(*Value->getAsSectionOffset());
-    return U->findRnglistFromOffset(*Value->getAsSectionOffset());
+      return U->findRnglistFromIndex(*SecOff);
+    return U->findRnglistFromOffset(*SecOff);
   }
   return DWARFAddressRangesVector();
 }

Comment on lines 398 to 400
if (!SecOff) {
return DWARFAddressRangesVector();
}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please omit the {} from single-line if statements like this.

Might be worth making this code a bit more consistent in the way it handles non-present optionals, since currentnly the two cases right next to each other are handled differently (one with an if, the other with an if!+early return). I guess the early return might be preferable, consistent with LLVM's style preference to reduce indentation:

optional Value = ...
if (!Value)
  return;
optional SecOff = ...
if (!SecOff)
  return;
...

Also - can you include a test case that demonstrates/validates this bug/fix?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I fixed the coding in the commit 394adb0.

How would you like to have the test case? Should I include the binary attached to the description of this issue in the LLVM repo?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We try to avoid checking in binary files, especially unbounded ones/ones without source code/asm code we could use to regenerate them.

Could you run the fixed dwarfdump on your test case, dump it out, then try to create a test case in assembly by hand that is minimal and exercises the interesting codepath (ie: crashes without this patch applied)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants