https://bugs.llvm.org/show_bug.cgi?id=44748
Bug ID: 44748
Summary: ObjectFile/ELF tests fail due to mismatched ID
Product: lldb
Version: 10.0
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: All Bugs
Assignee: lldb-dev@lists.llvm.org
Reporter: mgo...@gentoo.org
CC: jdevliegh...@apple.com, lab...@google.com,
llvm-b...@lists.llvm.org
lldb-shell :: ObjectFile/ELF/PT_LOAD-overlap-PT_INTERP.yaml
lldb-shell :: ObjectFile/ELF/PT_LOAD-overlap-PT_TLS.yaml
lldb-shell :: ObjectFile/ELF/PT_LOAD-overlap-section.yaml
lldb-shell :: ObjectFile/ELF/PT_LOAD.yaml
lldb-shell :: ObjectFile/ELF/PT_TLS-overlap-PT_LOAD.yaml
All of them seem to suffer from expecting 64-bit ID in output but getting
32-bit value instead, e.g.:
/home/mgorny/llvm-project.real/lldb/test/Shell/ObjectFile/ELF/PT_LOAD-overlap-PT_INTERP.yaml:8:15:
error: CHECK-NEXT: expected string not found in input
# CHECK-NEXT: ID: 0xfffffffffffffffe
^
<stdin>:11:2: note: scanning from here
ID: 0xfffffffe
^
I'm wondering whether this is intentional (i.e. tests need to be fixed) or the
code should be using a 64-bit unconditionally. If the former, should we try to
split the tests or maybe just hack it around in lldb-test?
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
