[swift-users] DWARF without DSYM

[Jim Ingham]

dsymutil is only given the .o files and the executable - same thing lldb sees.  So if it can find the module map to copy it into the dSYM, lldb can find it and load it without the dSYM.  So whether it does work or not, it should be able to.

Jim

> On Aug 26, 2016, at 11:37 AM, Jordan Rose via swift-users <swift-users at swift.org> wrote:
> 
> I suppose it can, but in theory the module that goes into the dSYM wouldn't be the same as the one that gets used by clients of a library. (Example: the one in the dSYM needs to have info about private types.) Sean can probably explain better than I can.
> 
> Jordan
> 
> 
>> On Aug 26, 2016, at 9:36, Dmitry Shevchenko <dmishe at google.com> wrote:
>> 
>> I see. I thought LLDB can import modules independently of sources, isn't that what target.swift-module-search-paths option is for?
>> 
>> On Thu, Aug 25, 2016 at 4:15 PM Jordan Rose <jordan_rose at apple.com> 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 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 at swift.org> wrote:
>> >
>> > Can swiftc generate debug info without a separate dSYM bundle? -g option looks to always generate a dSYM.
>> > _______________________________________________
>> > swift-users mailing list
>> > swift-users at swift.org
>> > https://lists.swift.org/mailman/listinfo/swift-users
>> 
> 
> _______________________________________________
> swift-users mailing list
> swift-users at swift.org
> https://lists.swift.org/mailman/listinfo/swift-users