Re: [lldb-dev] Is there a just-my-code like debugging mode for LLDB?

2020-05-13 Thread Greg Clayton via lldb-dev
Adding Antonio Afonso since he did some work on speeding things up at Facebook for Android. Emre: what version of LLDB are you using? Top of tree? One from a package distro? > On May 13, 2020, at 3:00 PM, Greg Clayton wrote: > > So one idea is to improve the PlatformAndroid to use "adb" to

Re: [lldb-dev] Is there a just-my-code like debugging mode for LLDB?

2020-05-13 Thread Greg Clayton via lldb-dev
One reason to not only load your libraries is backtraces will be truncated for any stack frames that go through the system libraries. These tend to be in the stack traces a lot as we deal with Android all the time at Facebook... Greg > On May 8, 2020, at 9:07 AM, Emre Kultursay via lldb-dev >

Re: [lldb-dev] Is there a just-my-code like debugging mode for LLDB?

2020-05-13 Thread Emre Kultursay via lldb-dev
Thanks for all the feedback and ideas. After Jim's comment about iOS performance, I decided to dig deeper to figure out why it's much slower to attach on Android compared to iOS. I identified an ipv6/ipv4 issue about adb and the simple fix (llvm.org/D79757) brought warm cache attach time down

Re: [lldb-dev] Is there a just-my-code like debugging mode for LLDB?

2020-05-13 Thread Greg Clayton via lldb-dev
So one idea is to improve the PlatformAndroid to use "adb" to copy all system libraries over and pre-cache all system libraries instead of letting it happen one by one. Android is also very inefficient in loading shared libraries. It will load them one by one and each one involves 2 stops

[lldb-dev] [Bug 45920] New: lldb wrongly stopped at a statement for nesting loop using step instruction

2020-05-13 Thread via lldb-dev
https://bugs.llvm.org/show_bug.cgi?id=45920 Bug ID: 45920 Summary: lldb wrongly stopped at a statement for nesting loop using step instruction Product: lldb Version: unspecified Hardware: PC OS: Linux

[lldb-dev] [Bug 45921] New: lldb not directly stopped at a specified statement

2020-05-13 Thread via lldb-dev
https://bugs.llvm.org/show_bug.cgi?id=45921 Bug ID: 45921 Summary: lldb not directly stopped at a specified statement Product: lldb Version: unspecified Hardware: PC OS: Linux Status: NEW Severity:

[lldb-dev] [Bug 45905] New: [lldb][unittest] Assertion failed : (m_replayers.find(RunID) == m_replayers.end())

2020-05-13 Thread via lldb-dev
https://bugs.llvm.org/show_bug.cgi?id=45905 Bug ID: 45905 Summary: [lldb][unittest] Assertion failed : (m_replayers.find(RunID) == m_replayers.end()) Product: lldb Version: unspecified Hardware: PC OS:

[lldb-dev] [Bug 45905] [lldb][unittest] Assertion failed : (m_replayers.find(RunID) == m_replayers.end())

2020-05-13 Thread via lldb-dev
https://bugs.llvm.org/show_bug.cgi?id=45905 Jonas Devlieghere changed: What|Removed |Added Assignee|lldb-dev@lists.llvm.org |jdevliegh...@apple.com -- You are

[lldb-dev] [Bug 45902] New: Wrong Debug Information at O3

2020-05-13 Thread via lldb-dev
https://bugs.llvm.org/show_bug.cgi?id=45902 Bug ID: 45902 Summary: Wrong Debug Information at O3 Product: lldb Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: enhancement