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
atest version of dwarflint?
Date: Thursday, September 21, 2017 21:00 CEST
From: Mark Wielaard
To: Djordje Todorovic , "Ananthakrishna Sowda
(asowda)"
CC: "elfutils-devel@sourceware.org"
References: <81113170-f590-4c51-bea0-c8ef3a442...@contoso.com>
<1501751
> Do you have patches against the origin/dwarf branch that contained the
>original dwarlint? Or against current master (or the 0.170 release)
>branch?
I have patches that can be applied on top of 0.170 release. I have moved dwarflint and libdw/c++ directories from origin/dwarf branch and then add
> BTW. The *bz2 test binaries under dwarflint/tests were not in the zip
> file. If any of them didn't come from the dwarf branch could you sent
> them separately?
Are you applied the patch 0002-Add-dwarflint-from-origin-dwarf-branch.patch
with 'git apply'?
Because, the 'patch' command would not i
Hi David,
This looks good to me, but Mark or someone else must approve.
Thanks,
Djordje
On 23.02.2018. 15:54, David Malcolm wrote:
> I attempted to build the "dwarflint" branch with gcc 7.3.1 , but ran
> into various problems of the form:
>
> c++/known.cc:220:1: error: explicit specialization o
ccing David
On 23.02.2018. 17:47, Djordje Todorovic wrote:
> Hi David,
>
> This looks good to me, but Mark or someone else must approve.
>
> Thanks,
> Djordje
>
> On 23.02.2018. 15:54, David Malcolm wrote:
>> I attempted to build the "dwarflint" branch
