Re: [lldb-dev] New test summary results formatter

That seems reasonable. I'll work that in. -Todd > On Dec 3, 2015, at 4:55 PM, Zachary Turner wrote: > > It would also be nice if the summary statistics were printed after the list > of failing / errored tests. The reason is that it involves a fixed number of > lines to print the table, but t

Re: [lldb-dev] LLDB and Swift

Thanks, Kamil! -Todd > On Dec 3, 2015, at 5:02 PM, Kamil Rytarowski wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Very nice. Congrats on your release! > >> On 04.12.2015 00:03, Todd Fiala via lldb-dev wrote: >> Hi all, >> >> Earlier today, you may have heard that Swift wen

Re: [lldb-dev] LLDB and Swift

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Very nice. Congrats on your release! On 04.12.2015 00:03, Todd Fiala via lldb-dev wrote: > Hi all, > > Earlier today, you may have heard that Swift went open source over > at swift.org . I just wanted to take a moment > to ment

Re: [lldb-dev] New test summary results formatter

It would also be nice if the summary statistics were printed after the list of failing / errored tests. The reason is that it involves a fixed number of lines to print the table, but the list of failures and errors is a variable number of lines which could potentially be very long and push the sta

Re: [lldb-dev] Exclusively build and install LLDB?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Compatibility with wide range of LLVM or Clang releases is out of scope. On 02.12.2015 17:38, Todd Fiala wrote: > Yes, that concept came out in the thread. I just wanted to make > sure there wasn't also a desire to park on a version of llvm/clang,

Re: [lldb-dev] Exclusively build and install LLDB?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 02.12.2015 19:36, Jim Ingham wrote: > Todd is right, at runtime lldb does need to find some of the clang > include files in order to build modules for its own purposes. On > an OS X install, these headers are put in: > > LLDB.framework/Resources

[lldb-dev] LLDB using Valgrind's embedded gdbserver

Hello, I am working on enhancing Valgrind's embedded gdbserver to allow LLDB to use it (https://bugs.kde.org/show_bug.cgi?id=356174 ). After adding support for 'qC' packets to the embedded gdbserver, LLDB is able to continue the halted program running under Valgrind; however, a short moment later

[lldb-dev] LLDB and Swift

Hi all, Earlier today, you may have heard that Swift went open source over at swift.org. I just wanted to take a moment to mention the Swift debugger and REPL and how they relate to LLDB. Swift’s Debugger and REPL are built on LLDB’s source-level plug-in architecture. As such, the Swift Debugge

Re: [lldb-dev] New test summary results formatter

Ahh I read further and see this was already mentioned by Pavel. On Thu, Dec 3, 2015 at 10:06 AM Zachary Turner wrote: > On Wed, Dec 2, 2015 at 10:20 PM Todd Fiala wrote: > >> On Wed, Dec 2, 2015 at 9:48 PM, Zachary Turner >> wrote: >> >>> >>> >>> On Wed, Dec 2, 2015 at 9:44 PM Todd Fiala wrot

Re: [lldb-dev] New test summary results formatter

On Wed, Dec 2, 2015 at 10:20 PM Todd Fiala wrote: > On Wed, Dec 2, 2015 at 9:48 PM, Zachary Turner wrote: > >> >> >> On Wed, Dec 2, 2015 at 9:44 PM Todd Fiala wrote: >> >>> >>> and the classname could be dropped (there's only one class per file anyway, so the classname is just wasted

Re: [lldb-dev] Custom expression evaluation target options

Each expression has a language so we should be able to get the Language* for renderscript: lldb_private::Language* language = lldb_private::Language::FindPlugin (m_expr.GetLanguage()); Then you can add a new virtual class on lldb_private::Language that can get any additional compiler flag

[lldb-dev] Custom expression evaluation target options

Hello all I've recently tracked down a problem in the expression evaluation engine for lldb, and I'm hoping for some historical context, and possibly some direction on the most appropriate fix. ## Problem I'd like to be able to set some target options for the JIT when calling `expr myRender

Re: [lldb-dev] New test summary results formatter

On Thu, Dec 3, 2015 at 1:41 AM, Pavel Labath wrote: > There is already code that enforces unique names (see dotest.py:1255). > How long ago was that added? I literally hit this within the last 6-8 weeks on something internal. > I added this a while back because we were getting test flakyness

Re: [lldb-dev] New test summary results formatter

There is already code that enforces unique names (see dotest.py:1255). I added this a while back because we were getting test flakyness because of that. I don't remember the exact reason but I think it had something to do with the log file names clashes, as all logs are placed in the same folder.

Re: [lldb-dev] reply: reply?? lldb debug jit-compiled code with llvm on windows

Problem solved. JIT debugging can be performed On the windows. thank you very much! -- The original message -- From: "Oleksiy Vyalov";; Data: 2015??12??3??AM 10:16 Receive: " "; Cc: "Zachary Turner"; "lldb-dev"; "Tamas Berghammer"; Title: Re: [l