<table><tr><td style="">danders added a comment.
</td></tr></table><br /><div><div><blockquote style="border-left: 3px solid #8C98B8;
color: #6B748C;
font-style: italic;
margin: 4px 0 12px 0;
padding: 8px 12px;
background-color: #F8F9FC;">
<div style="font-style: normal;
padding-bottom: 4px;">In <a href="https://phabricator.kde.org/T3689#175818" style="background-color: #e7e7e7;
border-color: #e7e7e7;
border-radius: 3px;
padding: 0 4px;
font-weight: bold;
color: black;text-decoration: none;">T3689#175818</a>, <a href="https://phabricator.kde.org/p/knauss/" style="
border-color: #f1f7ff;
color: #19558d;
background-color: #f1f7ff;
border: 1px solid transparent;
border-radius: 3px;
font-weight: bold;
padding: 0 4px;">@knauss</a> wrote:</div>
<div style="margin: 0;
padding: 0;
border: 0;
color: rgb(107, 116, 140);"><p>So far I understood abi-dumper is something different - I use abi-complience-checker to create those dumps.</p></div>
</blockquote>
<p>Afaiu abi-dumper is the new way of creating dumps. From home page:<br />
"This new way is based on the analysis of the debug-info from binary objects. It's more reliable, faster and simple way. "<br />
Any particular reason for not to use abi-dumper? (Just curious)</p>
<p>Anyway, I compiled both stable and unstable versions myself, created dumps with abi-dumper and got a clean bill.<br />
So I'm pretty certain the problem reported on CI is not correct (but I have been wrong before).</p></div></div><br /><div><strong>TASK DETAIL</strong><div><a href="https://phabricator.kde.org/T3689">https://phabricator.kde.org/T3689</a></div></div><br /><div><strong>To: </strong>knauss, danders<br /><strong>Cc: </strong>danders, davidedmundson, dfaure, kde-frameworks-devel, bcooksley, sysadmin, scarlettclark, aacid, knauss, alexeymin, kaning, blazquez<br /></div>