Re: [Dwarf-Discuss] debug_names - what should go in ?

On 04/10/2018 08:33 AM, Pavel Labath via Dwarf-Discuss wrote: I believe it makes sense to include both of these things in the index (including the implicitly-named imported declarations), however I would also like to stick to the specification as much as possible. I know the spec gives

Re: [Dwarf-Discuss] Location list entries for caller-saved registers at time of call

On 12/07/2018 08:12 AM, Jakub Jelinek wrote: On Fri, Dec 07, 2018 at 07:57:23AM -0800, Michael Eager wrote: On 12/07/2018 04:54 AM, Jakub Jelinek wrote: On Fri, Dec 07, 2018 at 12:36:39PM +, David Stenberg via Dwarf-Discuss wrote: For calls, we need to distinguish the locations that are

Re: [Dwarf-Discuss] dsymutil: "could not find referenced DIE" followed by a segmentation fault and other newbie questions

On 12/08/2018 06:24 AM, Gil Moses via Dwarf-Discuss wrote: Hi, Building with Xcode 7, once in a while I get the following warnings from the dsymutil tool (a few dozens): "could not find referenced DIE" Followed be a segmentation fault. Adding the verbosity flag, I got detailed information

Re: [Dwarf-Discuss] dwarf stack operator for byte swap.

Hi Chirag -- Thanks for your submission. It was received. I'm redesigning the DWARF website, in part to address the problem that it receives a lot of spam submissions. Your issue will be posted soon. On 11/7/19 10:51 PM, Chirag Patel wrote: Hi all, I have sent a comment through

Re: [Dwarf-Discuss] dwarf stack operator for byte swap.

Hi Chirag -- The DWARF Committee is currently on hiatus. We will consider resuming meetings early next year. On 12/16/19 4:30 AM, Chirag Patel wrote: Hello Michael, Thanks for opening the issue. Can you kindly provide me with the details about what is the next step, till issue gets

Re: [Dwarf-Discuss] dwarf stack operator for byte swap.

Hi Chirag -- A byte-swap operator would be a reasonable addition to the DWARF interpreter. In addition to writing a proposal as Paul suggests, one option I would recommend you consider is to create a user-defined operation to perform this byte-swap operation and give it a value in the range

Re: [Dwarf-Discuss] variable locations - safe use as lvalues

On 1/21/20 3:17 PM, Greg Clayton via Dwarf-Discuss wrote: On Jan 21, 2020, at 2:58 PM, Frank Ch. Eigler via Dwarf-Discuss wrote: Hi - While dwarfdump has 'check the DWARF' options available the location list overlap test is not done at all. The -kl option suggests it does loclist

Re: [Dwarf-Discuss] variable locations - safe use as lvalues

On 1/20/20 6:21 PM, Frank Ch. Eigler via Dwarf-Discuss wrote: Complication 2: The compiler reuses variable locations at the same PC. This seems to be a compiler bug. (Actually, this could be a valid optimization, e.g.: int a = expression; int b = expression; >

Re: [Dwarf-Discuss] variable locations - safe use as lvalues

On 1/20/20 2:20 PM, Frank Ch. Eigler via Dwarf-Discuss wrote: Hi - I have a question about variable location lists, but not their encoding, the use they are suitable for. The basic debugging scenario is just reading variable values, for which this is fine, especially when high-quality

Re: [Dwarf-Discuss] Use of Location Description operations in DWARF Expressions?

On 3/19/20 9:30 AM, David Stenberg via Dwarf-Discuss wrote: Hi! This is something that has popped up in a number of LLVM patch reviews, and is something that we would like to get some help with clarifying. For DWARF[345], may a DWARF Expression (described in section 2.5) contain any of the

Re: [Dwarf-Discuss] Use of Location Description operations in DWARF Expressions?

On 3/23/20 6:28 AM, Robinson, Paul via Dwarf-Discuss wrote: From: Dwarf-Discuss On Behalf Of Adrian Prantl via Dwarf-Discuss On Mar 19, 2020, at 5:49 PM, Michael Eager via Dwarf-Discuss disc...@lists.dwarfstd.org> wrote: My reading of sections 2.5 & 2.6 is that you cannot have a DW_O

Re: [Dwarf-Discuss] Use of Location Description operations in DWARF Expressions?

On 3/23/20 3:58 PM, Cary Coutant via Dwarf-Discuss wrote: I think that the description has become a bit less clear with the addition of the Implicit Location Descriptions in Section 2.6.1.1.4, which do compute values, rather than locations. Perhaps these should have been described in Section

Re: [Dwarf-Discuss] More on DW_AT_str_offset_base debug_str_offsets.dwo confusion

On 9/1/20 6:59 AM, David Anderson wrote: Mike Eager: please delete the new issue 200831.1 as it is simply wrong. Done. -- Michael Eager ___ Dwarf-Discuss mailing list Dwarf-Discuss@lists.dwarfstd.org

Re: [Dwarf-Discuss] John Bishop retiring from DWARF Committee

Hi John -- It looks like this went to the public DWARF discussion mailing list. I'm CCing the DWARF Committee mailing list. Thanks for your participation on the DWARF Committee. You contributions have been greatly appreciated. On 9/11/20 1:59 PM, Bishop, John E via Dwarf-Discuss wrote:

[Dwarf-Discuss] Subscriptions to DWARF-Discuss mailing list

I've noticed a number of what appear to be invalid subscriptions to the DWARF-Discuss mailing list, for example, stop-spoof...@amazon.com or spamred...@gmail.com. Invalid email addresses like this increase the number of notifications I see for bounced messages and may annoy the recipients,

Re: [Dwarf-Discuss] DW_AT_rnglists_base in DW_TAG_skeleton_unit

On 7/1/20 9:53 PM, Simon Marchi via Dwarf-Discuss wrote: Hi, The DW_AT_rnglists_base attribute is not listed in section 3.1.2 of DWARF5.pdf, which lists the allowed attributes for DW_TAG_skeleton_unit. However, in section 3.1.3, it says that the split full compile unit (the one in the .dwo)

Re: [Dwarf-Discuss] Segment selectors for the range list table.

On 7/15/20 9:49 PM, David Blaikie wrote: On Wed, Jul 15, 2020 at 7:07 PM Michael Eager via Dwarf-Discuss <mailto:dwarf-discuss@lists.dwarfstd.org>> wrote: Segmented addresses have been in the DWARF specification since Version 2   and AFAIK have not been changed since

Re: [Dwarf-Discuss] modeling different address spaces

On 7/16/20 2:23 AM, Metzger, Markus T via Dwarf-Discuss wrote: Hello, What would be the recommended way to model variables that are allocated to different address spaces? Can you describe the architecture a bit? I found DW_OPT_xderef for dereferencing address-space qualified pointers but

Re: [Dwarf-Discuss] modeling different address spaces

On 7/16/20 10:06 AM, Todd Allen via Dwarf-Discuss wrote: Markus, Michael, David, Xing, I always assumed that the segment support in DWARF was meant to be more general, and support architectures where there was no single flat memory, and so the segments were necessary for memory accesses. I

Re: [Dwarf-Discuss] modeling different address spaces

On 7/16/20 10:26 AM, John DelSignore via Dwarf-Discuss wrote: FYI, Tony Tye and his team at AMD created a DWARF Proposal for heterogeneous debugging, which is generally useful but required to debug optimized code for GPUs. It directly addresses the issue of how to model different address

Re: [Dwarf-Discuss] modeling different address spaces

On 7/20/20 1:43 AM, Metzger, Markus T via Dwarf-Discuss wrote: I also have a small proposal for describing locations as function of the SIMD lane by adding a DW_OP_push_simd_lane operator and introducing stack variants for piece operators. I have a write-up ready but wanted to wait until we

Re: [Dwarf-Discuss] modeling different address spaces

On 7/16/20 11:51 AM, David Blaikie wrote: On Thu, Jul 16, 2020 at 11:41 AM Robinson, Paul via Dwarf-Discuss The example that most often comes up is Harvard architectures.  As it happens, I think it's nearly always obvious from context whether a given address is data-segment or

Re: [Dwarf-Discuss] Segment selectors for the range list table.

Perhaps it's more like Paul was postulating - that the spec assumes code is in a code segment/doesn't need to be clarified. (but that gets a bit confused in debug_aranges - if it only is meant to contain code (not data), why does it need a segment selector - and also in the DIEs - if code is

Re: [Dwarf-Discuss] Segment selectors for the range list table.

On 7/16/20 1:36 PM, David Blaikie wrote: On Thu, Jul 16, 2020 at 1:07 PM Michael Eager > wrote: > Perhaps it's more like Paul was postulating - that the spec assumes code > is in a code segment/doesn't need to be clarified. (but that gets a bit

Re: [Dwarf-Discuss] Segment selectors for the range list table.

On 7/16/20 2:57 PM, David Blaikie wrote: On Thu, Jul 16, 2020 at 2:05 PM Michael Eager You appear to be starting with a counterfactual premise and using that to postulate a problem where none exists. Sorry - I seem to be misunderstanding what you mean by "there are no restrictions

Re: [Dwarf-Discuss] modeling different address spaces

On 7/20/20 8:24 AM, Metzger, Markus T wrote: Hello Michael, We'd also want an unbounded piece operator to describe partially registerized unbounded arrays, but I have not worked that out in detail, yet, and we're a bit farther away from an implementation. Can you describe this more?

[Dwarf-Discuss] DWARF Committee resumes meetings

The DWARF Debugging Standard Committee (http://dwarfstd.org) is planning to resume meetings starting in February. The DWARF debugging file format, as you likely know, is widely used by compilers and debuggers to support source level debugging. The Committee released Version 5 of the DWARF

Re: [Dwarf-Discuss] What to do with Pascal properties?

In 5/28/21 7:11 AM, Joost van der Sluis via Dwarf-Discuss wrote: Hi all, I am one of the Free Pascal developers and also work on a debugger, aimed towards Free Pascal. Now in Pascal there are 'properties'. Maybe you know these from c# which has something alike. Basically a property is an

Re: [Dwarf-Discuss] Retrieving variables, function address using dwarf

On 3/10/21 10:38 PM, Archana Deshmukh wrote: Thanks Michael for the response. Actually, I have only this much information. I need to get information related to  For global variables , I read the address "55b51afea000" from     > /proc//maps file. I use DW_OP_addr parameter to retrieve the

Re: [Dwarf-Discuss] compilers generating ABI non-compliant function calls?

On 3/9/21 7:13 AM, Frank Ch. Eigler via Dwarf-Discuss wrote: As I understand it, the location of*function return values* is however a gap in DWARF, and a consumer tool must resort to ABI specs. (Thus the elfutils dwfl_module_return_value_location() function.) I'm sure there's a Reason for

Re: [Dwarf-Discuss] Retrieving variables, function address using dwarf

It's difficult to offer advice with such a spare description. You might read the executable and relocate the .debug_info and other debug sections using the process map. If you have the process image, this probably would not be necessary. On 3/8/21 1:49 AM, Archana Deshmukh via Dwarf-Discuss

Re: [Dwarf-Discuss] compilers generating ABI non-compliant function calls?

On 3/9/21 7:05 AM, Andrew Cagney via Dwarf-Discuss wrote: Part of a typical Application Binary Interface is to specify the function calling convention. Several uses are: - ensuring function calls across interface boundaries work (function in one object calls function in second object) - the

Re: [Dwarf-Discuss] compilers generating ABI non-compliant function calls?

On 3/10/21 1:28 PM, David Blaikie wrote: On Wed, Mar 10, 2021 at 1:21 PM Cary Coutant > wrote: > Speculation beyond the original question: > Given that it's a pretty common/core feature of a debugger to call functions, perhaps a start would be some way

Re: [Dwarf-Discuss] HTML documentation for DWARF

On 3/1/21 2:53 PM, Konrad Kleine via Dwarf-Discuss wrote: On a side note, the comment function doesn't work: http://www.dwarfstd.org/Comment.php . The verification doesn't work there: "Verification failed. Please go back and try again." Make sure that

Re: [Dwarf-Discuss] Retrieving variables, function address using dwarf

On 3/5/21 8:28 PM, Archana Deshmukh via Dwarf-Discuss wrote: I need to read the address of local variable, global variable, function name and function arguments from the process. For global variables , I read the address "55b51afea000" from /proc//maps file. I use DW_OP_addr parameter to

Re: [Dwarf-Discuss] DW_AT values unknown to me.

Green Hills has never contacted us about DWARF implementation or submitted any proposals to the DWARF Committee. Many years ago, I was on an ABI committee with Greg Davis, who I believe is Director of Engineering at GHS. You might contact him for information about these attributes. The last

Re: [Dwarf-Discuss] How to interpret DW_AT_artificial tag?

On 2/28/22 13:11, David Blaikie via Dwarf-Discuss wrote: On Mon, Feb 28, 2022 at 12:55 PM Greg Clayton via Dwarf-Discuss You could choose to not show this, but I find it is often easier to show this information in case some compiler change in the future marks something that you

Re: [Dwarf-Discuss] Corner-cases with bitfields

On 5/6/22 10:11, Lancelot SIX via Dwarf-Discuss wrote: Dear all, During our work on debugging support of compute workloads on AMDGPU[1], we (at AMD) have been seeing two cases regarding description of bitfields in DWARF for which we do not find definitive answers in the DWARF documentation.

Re: [Dwarf-Discuss] Unnamed zero sized bit-fields (Re: Corner-cases with bitfields)

On 5/10/22 04:10, Pedro Alves via Dwarf-Discuss wrote: On 2022-05-06 18:11, Lancelot SIX via Dwarf-Discuss wrote: 2 - Unnamed zero sized bitfield Another case we met is related to unnamed fields with a size of 0 bits. Such field is defined in the c++ standard as (in 9.6 Bit-Fields): > As a

Re: [Dwarf-Discuss] EXTERNAL: Corner-cases with bitfields

On 5/10/22 02:15, Pedro Alves via Dwarf-Discuss wrote: But still, at the language level, the types ARE different. And DWARF is also about language source to machine code mapping. C/C++ don't let you take the address of a bitfield, for example, so it's possible type expressions in the

Re: [Dwarf-Discuss] EXTERNAL: Corner-cases with bitfields

On 5/9/22 13:18, Pedro Alves via Dwarf-Discuss wrote: An issue here is that DWARF does say this, in (DWARF 5, 5.7.6 Data Member Entries, page 119): "If the size of a data member is not the same as the size of the type given for the

Re: [Dwarf-Discuss] EXTERNAL: Corner-cases with bitfields

On 5/9/22 16:00, Todd Allen via Dwarf-Discuss wrote: I suppose, if you didn't want to submit an issue, another solution would be to require the necessary tags & attributes in the ABI itself. We already expect ABI documents to provide things like register values, CFI initial values, and some

Re: [Dwarf-Discuss] Support for SourceLink in DWARF

Hi Eugene -- Please work with Tony Tye (cc'ed), the champion on this issue, to draft a more complete proposal. Much of the description on the Github reference for SourceLink is about the implementation in a PDB file and less about the what information is contained and how it is used. On

Re: [Dwarf-discuss] OTHER or arguably ENHANCEMENT: Logo

On 3/22/23 13:00, Ron Brender via Dwarf-discuss wrote: FWIW, the "master" in the DWARF .git distro is an .eps file not .png--not that that really matters. I don't know where it came from other than Michael gave it to me to use. The .eps does contain some Copyright lines, namely % Copyright