From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 91605 invoked by alias); 21 Jan 2016 16:17:02 -0000 Mailing-List: contact libabigail-help@sourceware.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Subscribe: Sender: libabigail-owner@sourceware.org Received: (qmail 91560 invoked by uid 48); 21 Jan 2016 16:16:58 -0000 From: "woodard at redhat dot com" To: libabigail@sourceware.org Subject: [Bug default/18941] Add a warning option to libabigail tools to report possible DWARF issues Date: Fri, 01 Jan 2016 00:00:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: libabigail X-Bugzilla-Component: default X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: woodard at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: dodji at redhat dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2016-q1/txt/msg00057.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=3D18941 --- Comment #2 from Ben Woodard --- Many of the cases which I think need warnings are more prosaic. If it comes along a case where the DWARF has been stripped or was never generated, then most if not all of the ABI verification is not being done. = This should be a higher priority warning. This could also remind people to point= the libabigail utilities toward an external debuginfo file. I would say that th= is is a high enough priority that it should be the default unless some --quiet option is passed on the command line. A lower priority warning would be a exported function entry point for a non-static function that exists in ELF but doesn't exist in the available DWARF. This is important because we need to know the things that we are not= yet examining. I thought the option should be something like -Wunexamined-funct= ions A similar situation is the one you mention where you have a forward declara= tion but no information about the class. -Wunexamined-classes I think that -Wunions probably should be there too. This would trip if libabigail found any unions in the DWARF and emit the union's name for manu= al verification. I do not recall seeing this in the release notes. We should probably have a note saying that unions are not examined for ABI compatibil= ity in the release notes. And finally because the number of these warnings will likely grow over time= we should probably have something like: -W which turns on common problems -Wall which turns on every single warning. --=20 You are receiving this mail because: You are on the CC list for the bug.