[llvm-bugs] [Bug 43811] New: Function extents are too long so uf @rip disassembles adjacent function

[via llvm-bugs]

https://bugs.llvm.org/show_bug.cgi?id=43811

            Bug ID: 43811
           Summary: Function extents are too long so uf @rip disassembles
                    adjacent function
           Product: clang
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: C++
          Assignee: unassignedclangbugs at nondot.org
          Reporter: brucedawson at chromium.org
                CC: blitzrakete at gmail.com, dgregor at apple.com,
                    erik.pilkington at gmail.com, llvm-bugs at lists.llvm.org,
                    richard-llvm at metafoo.co.uk

Created attachment 22731
  --> https://bugs.llvm.org/attachment.cgi?id=22731&action=edit
The overly long disassembly

While debugging crash/ce009bf184d28b27 (sorry, Chrome/Google specific repro) I
found that disassembling the crashing function gave confusing and
incorrectly-long results. The repro is to download the specified minidump, then
go:

.ecxr
.cls
uf @rip

The resulting output should, I believe, end after about 310-316 lines. Instead
it goes on for another ~580 lines, pulling in code from completely different
translation units.

The input address is not the problem. The same results happen if the start
address of the function is used.

I have attached the disassembly that I get.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20191026/e067fb66/attachment-0001.html>