public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Djordje Todorovic <djordje.todorovic@rt-rk.com>
To: "Ananthakrishna Sowda (asowda)" <asowda@cisco.com>,
	Mark Wielaard <mark@klomp.org>
Cc: "elfutils-devel@sourceware.org" <elfutils-devel@sourceware.org>
Subject: Re: Latest version of dwarflint?
Date: Thu, 21 Sep 2017 16:07:00 -0000	[thread overview]
Message-ID: <cc97238e-81a3-683b-a2ea-1e4d82382f40@rt-rk.com> (raw)
In-Reply-To: <624331B2-472C-44AD-9034-05AD3CBBAE8A@cisco.com>

Hi All,

I have managed to integrate dwarflint on the top of elfutils-0.170 release, so dwarflint and locstats can use all conveniences and improvements of the newest libdw library (such as 
handling ops like DW_OP_GNU_entry_value).

It is used internally by our compiler team. I have also managed to add some new enhancements for locstats, such as reporting summary either for formal parameter or local variable, 
reporting some kind of verbose info about particular variable or formal parameter of particular function.
But, beside these enhancements that were interested for our compiler team, dwarflint and locstats have a lot of good utilities that can be really useful to compiler developers. For 
example, dwarflint tool can detect mistakes in debug sections such as debug info, debug line etc., and help compiler developers to get rid of those mistakes. Locstats can 
apparently report useful summary and show progress of making better coverage for local variables or formal parameter in debug sections, so it can save a lot of time to compiler 
developers.

At least, maybe considering a making new branch called „dwarflint“ on elfuitls git repository, which follows the newest source code, would be good for the beginning, the same as it 
was on elfutils-0.152? Because, getting more feedback from users, these tools would be better and more useful, so it can be, one day, merged on to master branch.

If you are interested, I can share my patches.

Best regards,
Djordje Todorovic

On 21.09.2017. 17:59, Ananthakrishna Sowda (asowda) wrote:
> Any interest in seeing some patches which upgrade dwarflint to latest elfutils-0.170?    Djordje Todorovic  has more details about the patches.
> Thanks,
> Ananth
> 
> On 8/3/17, 2:13 AM, "Mark Wielaard" <mark@klomp.org> wrote:
> 
>      On Wed, 2017-08-02 at 19:47 +0000, Ananthakrishna Sowda (asowda) wrote:
>      > I found the dwarflint and locstats tools in the ‘dwarf ‘ branch of elfutils.
>      >    https://sourceware.org/elfutils/DwarfLint
>      > Any plans of merging this into main branch?
>      
>      Currently not, sorry.
>      
>      > I get following error from locstats:
>      >
>      > error: .debug_info: DIE 0x3f10fc: dwarf_getlocation_addr: invalid DWARF
>      >
>      > This error is reported on DW_OP_GNU_entry_value in DWARF location list. Any newer version of these tools which can handle DWARF5 ops such as DW_OP_GNU_entry-value?
>      
>      There is a standalone version of dwlocstat here:
>      https://github.com/pmachata/dwlocstat
>      
>      It should handle DW_OP_GNU_entry_value but is also a bit old so might
>      not handle the latest DWARF extensions.
>      
>      Cheers,
>      
>      Mark
>      
> 

  reply	other threads:[~2017-09-21 16:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-02 19:47 Ananthakrishna Sowda (asowda)
2017-08-03  9:13 ` Mark Wielaard
2017-09-21 15:59   ` Ananthakrishna Sowda (asowda)
2017-09-21 16:07     ` Djordje Todorovic [this message]
2017-09-21 19:00       ` Mark Wielaard
2017-09-22 13:37         ` Djordje Todorovic
2017-09-25 16:18           ` Mark Wielaard
2017-09-26 11:39             ` Djordje Todorovic
     [not found]             ` <c2b5f92f-0798-1e43-2095-b282bd5d7879@rt-rk.com>
2017-09-29 12:08               ` Mark Wielaard
2017-09-29 12:26                 ` Mark Wielaard
2017-09-29 12:44                   ` Djordje Todorovic
2017-09-29 13:07                     ` Mark Wielaard
2017-10-06 19:53                 ` Mark Wielaard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cc97238e-81a3-683b-a2ea-1e4d82382f40@rt-rk.com \
    --to=djordje.todorovic@rt-rk.com \
    --cc=asowda@cisco.com \
    --cc=elfutils-devel@sourceware.org \
    --cc=mark@klomp.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).