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: unassignedclangb...@nondot.org
Reporter: brucedaw...@chromium.org
CC: blitzrak...@gmail.com, dgre...@apple.com,
erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org,
richard-l...@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._______________________________________________
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
