Dear DWARF experts,
I have a question regarding the attribute DW_AT_segment. I do not quite
understand how to handle it, yet.
It can appear in a DIE (or its parent) whenever DW_AT_low_pc,
DW_AT_high_pc, DW_AT_ranges, DW_AT_entry_pc, or a location description that
evaluates to an Address are used.
in question. So this little sentence implies a lot of
difficulties for a consumer.
Kind regards,
Jayvee
Am Do., 26. Sept. 2019 um 23:12 Uhr schrieb Michael Eager :
> On 9/26/19 3:33 AM, Jayvee Neumann via Dwarf-Discuss wrote:
> > Dear DWARF experts,
> >
> > I have a q
is set as you descend the
> parse tree, pushing previous values, and popped when ascend the tree.
>
> Almost all architectures, and specifically the ARM and AMD64
> architectures you mention, use linear, not segmented, address spaces.
>
> >
> > Kind regards,
> > Jayv
Hello together,
I am trying to consume the file name of a compile unit. Fortunately
DW_TAG_compile_unit has a member DW_AT_name and DW_AT_comp_dir.
Unfortunately it is not clear which kind of encoding is used to store these
strings. I tried around with GCC and clang. GCC under Windows produces
lat
Hello together!
I am running into a problem while performing a stack trace of x86 code. The
assembly code I am running has been generated by mingw from C++ code and
looks like this:
6c9c1210 <__ZN7my_class9my_methodEs>:
6c9c1210: sub$0x1c,%esp
6c9c1213: mov0x20(%esp),%edx
6c9c1217: mov
