[lldb-dev] [Bug 45981] New: StringRef::getAsInteger doesn't support "+1"
https://bugs.llvm.org/show_bug.cgi?id=45981 Bug ID: 45981 Summary: StringRef::getAsInteger doesn't support "+1" Product: lldb Version: unspecified Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: lldb-dev@lists.llvm.org Reporter: jing...@apple.com CC: jdevliegh...@apple.com, llvm-b...@lists.llvm.org (lldb) set set interpreter.expand-regex-aliases 1 (lldb) jump +1 thread jump --by +1 error: invalid line offset: '+1'. And indeed: (lldb) thread jump --by +1 error: invalid line offset: '+1'. The option parser calls: option_arg.getAsInteger(0, m_line_offset); where m_line_offset it the storage for the integer read in. Either StringRef::getAsInteger should support this, or we should strip off the leading +. -- 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
[lldb-dev] LLVM 10.0.1-rc1 release update
Hi, All the patches for LLVM 10.0.1-rc1 have been merged, and I'm just waiting for the CI jobs to finish. I will tag the release tomorrow if all goes well. Don't worry if you have a change that didn't make it into LLVM 10.0.1-rc1, there is still another month to merge changes before LLVM 10.0.1-rc2. -Tom ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [Bug 43561] Unwind augmentation on x86 is off by one instruction
https://bugs.llvm.org/show_bug.cgi?id=43561 Jaroslav Sevcik changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- 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
[lldb-dev] [Bug 44331] LLDB crashes in expression evaluation (in codegen)
https://bugs.llvm.org/show_bug.cgi?id=44331 Jaroslav Sevcik changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- 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
[lldb-dev] [Bug 45988] New: SBValue.GetNumChildren() returns wrong value for double indirections
https://bugs.llvm.org/show_bug.cgi?id=45988
Bug ID: 45988
Summary: SBValue.GetNumChildren() returns wrong value for
double indirections
Product: lldb
Version: 10.0
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: All Bugs
Assignee: lldb-dev@lists.llvm.org
Reporter: ja...@google.com
CC: jdevliegh...@apple.com, llvm-b...@lists.llvm.org
SBValue::GetNumChildren seems to look through two pointer indirections, but
SBValue::GetChildAtIndex only through one.
If we have a value with pointer to a pointer to a struct, then GetNumChildren()
on that value will return the number of fields of the struct, but
GetChildAtIndex(0) will return the pointer to the struct and GetChildAtIndex(1)
will return the Invalid SBValue sentinel.
Repro:
```
$ cat a.cc
struct Inner
{
int a;
int b;
};
struct Outer
{
Inner *inner;
};
int main()
{
Inner inner{42, 56};
Outer outer{&inner};
return 0; // break here
}
$ cat a.py
import lldb
import os
debugger = lldb.SBDebugger.Create()
debugger.SetAsync(False)
target = debugger.CreateTargetWithFileAndTargetTriple("a.out",
"x86_64-pc-linux")
main_bp = target.BreakpointCreateByLocation("a.cc", 16)
process = target.LaunchSimple (None, None, os.getcwd())
thread = process.selected_thread
frame = thread.GetSelectedFrame()
print(frame.EvaluateExpression("&(outer.inner)").GetNumChildren())
print(frame.EvaluateExpression("&(outer.inner)").GetChildAtIndex(0))
print(frame.EvaluateExpression("&(outer.inner)").GetChildAtIndex(1))
$ python a.py
2
(Inner *) *$1 = 0x7ffedf89e290
No value
```
--
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
