R-2654
>
> On Wed, Feb 22, 2017 at 3:10 PM, Jordan Rose via swift-users <
> swift-users@swift.org> wrote:
>
> #selector(FileHandle.readToEndOfFileInBackgroundAndNotify as (FileHandle)
> -> (Void) -> Void)
>
> Sorry. :-(
> Jordan
>
>
> > On Feb 2
#selector(FileHandle.readToEndOfFileInBackgroundAndNotify) throws an error:
Ambiguous use of 'readToEndOfFileInBackgroundAndNotify'
So I've tried to specify it a bit more (notice the parens):
#selector(FileHandle.readToEndOfFileInBackgroundAndNotify())
Ambiguous reference to member
'readToEndO
.
>> > >
>> > > Jordan
>> > >
>> > >
>> > >> On Aug 26, 2016, at 9:36, Dmitry Shevchenko
>> wrote:
>> > >>
>> > >> I see. I thought LLDB can import modules independently of sources,
>>
ion is for?
> > >>
> > >> On Thu, Aug 25, 2016 at 4:15 PM Jordan Rose
> wrote:
> > >> Plain DWARF isn't sufficient to debug a Swift program (we actually
> stuff the entire swiftmodule into the dSYM), but if you just want to trace
> e
ces,
>> isn't that what target.swift-module-search-paths option is for?
>> >>
>> >> On Thu, Aug 25, 2016 at 4:15 PM Jordan Rose
>> wrote:
>> >> Plain DWARF isn't sufficient to debug a Swift program (we actually
>> stuff the entire swift
x27;t that what target.swift-module-search-paths option is for?
> >>
> >> On Thu, Aug 25, 2016 at 4:15 PM Jordan Rose
> wrote:
> >> Plain DWARF isn't sufficient to debug a Swift program (we actually
> stuff the entire swiftmodule into the dSYM), but if you just wa
le into the dSYM), but if you just want to trace
> execution you should be able to use -gline-tables-only.
>
> Jordan
>
>
> > On Aug 25, 2016, at 13:10, Dmitry Shevchenko via swift-users <
> swift-users@swift.org> wrote:
> >
> > Can swiftc generate debug
Can swiftc generate debug info without a separate dSYM bundle? -g option
looks to always generate a dSYM.
___
swift-users mailing list
swift-users@swift.org
https://lists.swift.org/mailman/listinfo/swift-users
Hm actually it looks like the code I mentioned in (2) is not even executed
in this case. The flow goes through if (module) {} block and does not care
about target.swift-module-search-paths.
On Mon, Aug 22, 2016 at 5:08 PM Dmitry Shevchenko wrote:
> Hello,
>
> We build Swift code in a location di
Hello,
We build Swift code in a location different from where sources live and
having a bunch of issues with LLDB in such a setup.
One of the problems is LLDB not being able to import the modules referenced
from binaries we build:
error: Error in auto-import:
failed to get module '' from AST cont
10 matches
Mail list logo