New machine is up and running.
There is more power and it builds the whole distribution within 35 minutes.
On 04.10.2016 15:13, Kamil Rytarowski via lldb-dev wrote:
> Hello,
>
> I'm in process of switching a machine for NetBSD buildbot. It will be
> temporarily unavailable.
>
>
>
> __
This isn't the appropriate place to discuss lldb-swift build problems, since
the swift support is not actually in the llvm.org tree. A better mailing list
would be:
https://lists.swift.org/mailman/listinfo/swift-lldb-dev
Jim
> On Oct 5, 2016, at 12:25 PM, Rex Fenley wrote:
>
> Hey!
>
> I t
Hey!
I tried building the LLDB target from within Xcode in order to gain
understanding of how this system works at the source level. However, I get
the following error during compilation:
subprocess.CalledProcessError: Command '['python',
'/Users/Rex/Documents/projects/swift-lldb/llvm/tools/swift
That's totally fine for our use case.
On Wed, Oct 5, 2016 at 11:57 AM, Jim Ingham wrote:
> You would have to be really careful about using "debugger variables" whose
> name is not decorated with a "$". After all, this is introducing a global
> variable, which will be shadowed by local variables
You would have to be really careful about using "debugger variables" whose name
is not decorated with a "$". After all, this is introducing a global variable,
which will be shadowed by local variables, ivars, file statics for the current
frame's CU, etc. So using the code you've added at vario
Hey Kate! Thanks for all this info, it's really helpful :)
We'd like to have more complex expressions being used from the debugger.
Some of this would be code written in separate files. It will be difficult
or at least very tedious to have all our code use "$", is there a way to
void using "$"? Is
> On Oct 5, 2016, at 10:14 AM, Rex Fenley via lldb-dev
> wrote:
>
> Maybe I have that incorrectly, this does seem to work when using lldb from
> Xcode's console. This doesn't work when typing `lldb` into the terminal and
> using it from there. I assumed the two were the same.
The same underly
Sure, I'll file a bug :)
Can we get --top-level to work with Swift too?
On Wed, Oct 5, 2016 at 11:03 AM, Jim Ingham wrote:
>
> > On Oct 5, 2016, at 10:06 AM, Rex Fenley wrote:
> >
> > Jim,
> >
> > That doesn't seem to work for us. We're using lldb packaged with Xcode 8
> fyi.
> > (lldb) expr -
> On Oct 5, 2016, at 10:06 AM, Rex Fenley wrote:
>
> Jim,
>
> That doesn't seem to work for us. We're using lldb packaged with Xcode 8 fyi.
> (lldb) expr --top-level -- NSString *string = [NSString stringWithUTF8String:
> "This is a string"];
>
>
>
> ; Function Attrs: nounwind
>
> define i
Maybe I have that incorrectly, this does seem to work when using lldb from
Xcode's console. This doesn't work when typing `lldb` into the terminal and
using it from there. I assumed the two were the same.
On a separate note, --top-level doesn't seem to work for swift (from Xcode
console lldb). We
Jim,
That doesn't seem to work for us. We're using lldb packaged with Xcode 8
fyi.
(lldb) expr --top-level -- NSString *string = [NSString
stringWithUTF8String: "This is a string"];
; Function Attrs: nounwind
define internal void @_GLOBAL__sub_I__null_() #0 section
"__TEXT,__StaticInit,regular
11 matches
Mail list logo
