>>>:
>>>
>>>> On 9/26/19 3:33 AM, Jayvee Neumann via Dwarf-Discuss wrote:
>>>> > Dear DWARF experts,
>>>> >
>>>> > I have a question regarding the attribute DW_AT_segment. I do not quite
>>>> > understand how to
On 9/27/19 1:29 AM, Jayvee Neumann wrote:
Thank you Michael and Ron,
what I am trying to do is write a consumer that is able to handle images
from several targets: i386, AMD64, and also ARM. The target images will
be loaded and running (and debugged during run-time).
I want to find a way to ha
Jayvee,
If you are dealing with a linear 32- or 64-bit address space then there are
no segments to worry about, so the question is moot. If you are dealing
with a segmented address space, then the problems you describe are exactly
those that debuggers on segmented machine dealt with all the time.
gt; >
>>> > Assume, I have an attribute DW_AT_low_pc. If there is no DW_AT_segment,
>>> > this attribute is simply the low_pc as it was determined during
>>> > compile-time. While debugging, this value has to be relocated if the
>>> > image had be
Evaluating the expression could also
>> > incorporate the usage of run-time information and relocated addresses
>> > (i.e. the DS/CS/SS registers).
>> >
>> > I hope I was able to articulate my question well, English is not my
>> > native languag
Thank you Michael and Ron,
what I am trying to do is write a consumer that is able to handle images
from several targets: i386, AMD64, and also ARM. The target images will be
loaded and running (and debugged during run-time).
I want to find a way to handle addresses in a simple way, abstracting fr
