public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mike Frysinger" <vapier@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/sandbox:master commit in: libsbutil/
Date: Sun, 27 Nov 2016 18:31:40 +0000 (UTC)	[thread overview]
Message-ID: <1480271436.87d6537245b6f7cbf028e4c0e187cda7484729f0.vapier@gentoo> (raw)

commit:     87d6537245b6f7cbf028e4c0e187cda7484729f0
Author:     Guenther Brunthaler <gb_about_gnu <AT> gmx <DOT> net>
AuthorDate: Sun Nov 27 18:30:36 2016 +0000
Commit:     Mike Frysinger <vapier <AT> gentoo <DOT> org>
CommitDate: Sun Nov 27 18:30:36 2016 +0000
URL:        https://gitweb.gentoo.org/proj/sandbox.git/commit/?id=87d65372

libsbutil: elide sb_maybe_gdb when -DNDEBUG is used

Since sb_maybe_gdb is set up as a stub macro, make sure we don't define
the function either to cut down on size and build failures (when the
macro tries to expand the function prototype).

URL: https://bugs.gentoo.org/600550

 libsbutil/sb_gdb.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/libsbutil/sb_gdb.c b/libsbutil/sb_gdb.c
index 6112379..021a3c4 100644
--- a/libsbutil/sb_gdb.c
+++ b/libsbutil/sb_gdb.c
@@ -62,6 +62,7 @@ void sb_gdb(void)
 	}
 }
 
+#ifndef NDEBUG
 void sb_maybe_gdb(void)
 {
 	if (is_env_on("SANDBOX_GDB")) {
@@ -69,3 +70,4 @@ void sb_maybe_gdb(void)
 		sb_gdb();
 	}
 }
+#endif


             reply	other threads:[~2016-11-27 18:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-27 18:31 Mike Frysinger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-06-09  5:03 [gentoo-commits] proj/sandbox:master commit in: libsbutil/ Sam James
2025-03-09 18:09 Mike Gilbert
2023-07-17 13:54 Mike Gilbert
2021-11-05 10:25 Mike Frysinger
2021-11-03 21:10 Andreas K. Hüttel
2021-11-03  4:59 Mike Frysinger
2021-10-18  8:48 Mike Frysinger
2016-01-18  6:18 Mike Frysinger
2015-12-20  8:41 Mike Frysinger
2015-09-20  8:15 Mike Frysinger
2015-09-11  7:53 Mike Frysinger
2015-09-11  7:53 Mike Frysinger
2015-09-11  7:53 Mike Frysinger
2013-02-25  4:08 Mike Frysinger
2012-12-24  5:23 Mike Frysinger
2012-12-24  5:19 Mike Frysinger
2012-11-26 10:10 Mike Frysinger

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=1480271436.87d6537245b6f7cbf028e4c0e187cda7484729f0.vapier@gentoo \
    --to=vapier@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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