Re: lldb: 'CompileUnit' and 'LineEntry' are wrong
Re: lldb: 'CompileUnit' and 'LineEntry' are wrong
- Subject: Re: lldb: 'CompileUnit' and 'LineEntry' are wrong
- From: email@hidden
- Date: Thu, 12 Dec 2013 11:38:00 -0800
Yes, that is correct. If you are seeing paths from someone else's machine, then the code you are debugging comes from a build done on that machine.
Jim
On Dec 12, 2013, at 11:35 AM, Alexander von Below <email@hidden> wrote:
> Thank you, that helps a lot!
>
> But allow me a follow-up question: If those paths are wrong, can I assume that I am NOT actually using the library I think I am using (i.e. the one I built on my system)? As I said, the project is old and complex, so I am would like to make sure …
>
> Alex
>
> Am 12.12.2013 um 20:19 schrieb email@hidden:
>
>> The file paths for CompileUnits and LineEntries come from the debug information, which is written at the time the library is built, and thus records the paths at compilation time. If you have the source tree somewhere on your system, you can point lldb at it using the "target.source-map" setting.
>>
>> (lldb) settings list target.source-map
>> target.source-map -- Source path remappings used to track the change of
>> location between a source file when built, and where it exists on the
>> current system. It consists of an array of duples, the first element of
>> each duple is some part (starting at the root) of the path to the file when
>> it was built, and the second is where the remainder of the original build
>> hierarchy is rooted on the local system. Each element of the array is
>> checked in order and the first one that results in a match wins.
>>
>> Hope this helps,
>>
>> Jim
>>
>> On Dec 12, 2013, at 10:06 AM, Alexander von Below <email@hidden> wrote:
>>
>>> Hello all,
>>>
>>> I have taken over a pretty old and rather murky project. It contains a C++ static lib.
>>>
>>> Now, whenever I want to step into the static lib, I only see assembly code.
>>>
>>> You may think that my question is "Why?", but actually I can answer that!
>>>
>>> The 'CompileUnit' and the 'LineEntry' (which I can see from lldb's image lookup command) are wrong. Or rather, they contain the paths on someone else's machine. Not mine.
>>>
>>> NOW I am asking: "Why?". And how can I find out what is going wrong?
>>>
>>> Thanks a lot
>>>
>>> Alex
>>> _______________________________________________
>>> Do not post admin requests to the list. They will be ignored.
>>> Xcode-users mailing list (email@hidden)
>>> Help/Unsubscribe/Update your Subscription:
>>>
>>> This email sent to email@hidden
>>
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden