https://bugs.llvm.org/show_bug.cgi?id=36687
lab...@google.com changed:
What|Removed |Added
Assignee|lldb-dev@lists.llvm.org |lab...@google.com
CC|
https://bugs.llvm.org/show_bug.cgi?id=36692
Bug ID: 36692
Summary: "frame variable" reports incorrect values for structs
with float fields
Product: lldb
Version: 5.0
Hardware: PC
OS: MacOS X
https://bugs.llvm.org/show_bug.cgi?id=36694
Bug ID: 36694
Summary: LLDB compile error on s390x: "
Product: lldb
Version: 6.0
Hardware: Other
OS: Linux
Status: NEW
Severity: normal
Priority: P
On Mon, Mar 12, 2018 at 7:01 PM, Jim Ingham wrote:
> The problem with having no timeouts is that you have to then be fairly
> careful how you write tests. You can't do:
>
> while (1) {
>print("Set a breakpoint here and hit it a few times then stop the test");
> }
>
>
If this is a Mac I would recommend to build both lldbs in RelWithDebInfo mode
and then run them through Instruments and compare the traces. I'd be very
interested in learning what the cause for the slowdown is.
-- adrian
> On Mar 12, 2018, at 2:57 PM, Timothee Cour
after further inspection it turns out it's a performance regression
between llvm 5 and llvm 6:
$homebrew_D/Cellar/llvm/5.0.1/lldb -s test_lldb.txt -- prog
8 seconds
$homebrew_D/Cellar/llvm/6.0.0/bin/lldb -s test_lldb.txt -- prog
40 seconds
cat test_lldb.txt:
```
b FOO
r
bt
q
```
prog is some
On Fri, Mar 9, 2018 at 3:45 AM, Pavel Labath wrote:
>
>
>
> On Thu, 8 Mar 2018 at 18:40, Davide Italiano wrote:
>>
>> On Thu, Mar 8, 2018 at 10:29 AM, Greg Clayton wrote:
>> > It would be great to look into these and see what is
The problem with having no timeouts is that you have to then be fairly careful
how you write tests. You can't do:
while (1) {
print("Set a breakpoint here and hit it a few times then stop the test");
}
because if the breakpoint setting fails the test can run forever. And we wait
forever
Have you tried diff'ing your cmake invocation against the on used by homebrew?
-- adrian
> On Mar 9, 2018, at 12:59 AM, Timothee Cour via lldb-dev
> wrote:
>
> while testing out https://github.com/llvm-mirror/lldb/pull/3 I noticed
> that when I compiled lldb from