Re: [lldb-dev] [3.8 Release] Release status

I had hoped to tag rc3 today (I feel like I've said this a lot lately), but it's at least really, really close. I'm waiting for: - r261297 - Implement the likely resolution of core issue 253. Still in post-commit review. - D17507 - The controlling expression for _Generic is unevaluated New fo

Re: [lldb-dev] Module Cache improvements - RFC

Can't you just cache the modules locally on the disk, so that you only take that 26 second hit the first time you try to download that module, and then it indexes it by some sort of hash. Then instead of just downloading it, you check the local cache first and only download if it's not there. If

Re: [lldb-dev] lldb-mi and shared library path

The Hexagon SDK taking to hardware is very bare bones. The OS is sitting on the phone and is loaded to the Hexagon by Android. The debugger opens the OS elf file, the user tells it where the shared libraries are, and lldb does the usual stop-at-the-rendezvous function negotiation to get info whe

Re: [lldb-dev] Module Cache improvements - RFC

> On Jan 28, 2016, at 4:21 AM, Pavel Labath wrote: > > Hello all, > > we are running into limitations of the current module download/caching > system. A simple android application can link to about 46 megabytes > worth of modules, and downloading that with our current transfer rates > takes abo

Re: [lldb-dev] Sending input to the process being debugged

You have to consume the events from the debugger's listener (unless you specify a different listener in your SBLaunchInfo or SBAttachInfo). We have python code that can show you how to consume events: svn cat http://llvm.org/svn/llvm-project/lldb/trunk/examples/python/process_events.py So eve

Re: [lldb-dev] lldb-mi and shared library path

> On Feb 4, 2016, at 1:51 PM, Ted Woodward via lldb-dev > wrote: > > I’d expect “-gdb-set solib-search-path” to call “target modules search-paths > add”, and it does, but only when the –target-remote command is issued. It > also doesn’t handle the multiple path case, :… > > I think it shoul

Re: [lldb-dev] problem with quoted strings in setting target.run-args

> On Feb 18, 2016, at 4:16 PM, Ted Woodward via lldb-dev > wrote: > > Quoted strings in target.run-args aren’t handled correctly. > > (lldb) settings set target.run-args "foo bar" > (lldb) settings show target.run-args > target.run-args (array of strings) = > [0]: "foo bar" > > This looks

[lldb-dev] [Bug 26632] Breakpoint opcode triggering SIGBUS on Nexus 6

https://llvm.org/bugs/show_bug.cgi?id=26632 Ewan Crawford changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[lldb-dev] [Bug 26694] New: Expression evaluation broken for__attribute__((overloadable))

https://llvm.org/bugs/show_bug.cgi?id=26694 Bug ID: 26694 Summary: Expression evaluation broken for__attribute__((overloadable)) Product: lldb Version: unspecified Hardware: PC OS: Windows NT Sta

[lldb-dev] [Bug 24717] MiBreakTestCase.test_lldbmi_break_insert_function_pending is marked expectedFlakeyLinux, but still fails

https://llvm.org/bugs/show_bug.cgi?id=24717 lab...@google.com changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED

[lldb-dev] [Bug 26677] LLDB does not report Linux signal 35 (SIGRTMIN+1)

https://llvm.org/bugs/show_bug.cgi?id=26677 lab...@google.com changed: What|Removed |Added Status|NEW |RESOLVED CC|