From: "dodji at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/19706] Core dump from abidiff with suppression
Date: Fri, 01 Jan 2016 00:00:00 -0000 [thread overview]
Message-ID: <bug-19706-9487-80HwxzVHpn@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-19706-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=19706
--- Comment #5 from dodji at redhat dot com ---
>
> [suppress_function]
> name_regexp = unity::scopes::internal::.*
>
> Without this suppression, I don't get a core dump.
>
> Is there a way to suppress all changes for absolutely everything in a
> particular namespace (preferably one that works with 1.0.rc2)?
I'd recommend to avoid using the [suppress_function] directive to suppress
change reports about function sub-types changes.
If you can, I believe it's more forward looking to use the [suppress_type]
directive.
Here is the rationale.
Usually, functions (or global variables) show up in the change report because o
one of their sub-types have changed.
If you suppress the change report about the whole function, if tomorrow another
sub-type of that function changes, you won't see it. But it could be harmful.
> We have a strict separation of public and private APIs. In particular, we
> use the pimpl idiom for the public API, and we have tests to enforce that no
> public header mentions anything that's in the internal namespace (other than
> the opaque pointer-to-impl, which is forward-declared).
This seems to mean that suppressing change reports about *types* that are
defined in the internal namespaces should usually be enough, e.g,
[suppress_type]
name_regexp = ^unity::scopes::internal::.*
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-02-24 17:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 0:00 [Bug default/19706] New: " michi.henning at canonical dot com
2016-01-01 0:00 ` [Bug default/19706] " michi.henning at canonical dot com
2016-01-01 0:00 ` michi.henning at canonical dot com
2016-01-01 0:00 ` dodji at redhat dot com [this message]
2016-01-01 0:00 ` michi.henning at canonical dot com
2016-01-01 0:00 ` dodji at redhat dot com
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=bug-19706-9487-80HwxzVHpn@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libabigail@sourceware.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).