On Fri, 26 Feb 2016 15:18:00 -0800
Greg Clayton wrote:
>
> That makes perfect sense. So will this be enough to get you going
> them?
>
I think so. I am curious what the correct way would be to use
the '--shlib' option would be since I couldn't get it to work.
I'm going to try creating a pyth
On Thu, 25 Feb 2016 10:18:42 -0800
Greg Clayton wrote:
>
> Yes: use the "target symbols add" to do thing manually:
>
> (lldb) target symbols add
> --shlib-name /path/to/my/workspace/bin/maci64/libA.dylib
> /archive/builds/1234/bin/maci64/libA.dylib.dSYM/Contents/Resources/DWARF/libA.dylib
>
> On Feb 26, 2016, at 3:06 PM, Mike Gulick wrote:
>
> On Thu, 25 Feb 2016 10:18:42 -0800
> Greg Clayton wrote:
>
>>
>> Yes: use the "target symbols add" to do thing manually:
>>
>> (lldb) target symbols add
>> --shlib-name /path/to/my/workspace/bin/maci64/libA.dylib
>> /archive/builds/1234/
> On Feb 24, 2016, at 4:21 PM, Mike Gulick via lldb-dev
> wrote:
>
> Hi lldb-dev,
>
> I'm trying to write some tooling to help with debugging complex builds on
> Mac. The libraries all have debugging info separated into .dSYM/
> directories. Due to some complexities in our build system, th
Hi lldb-dev,
I'm trying to write some tooling to help with debugging complex builds on Mac.
The libraries all have debugging info separated into .dSYM/ directories. Due
to some complexities in our build system, the .dSYM directories with the
debugging info have completely different base path
