From: zkabelac@sourceware.org <zkabelac@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2/libdm/mm dbg_malloc.c
Date: 28 Jan 2011 16:01:32 -0000 [thread overview]
Message-ID: <20110128160132.23140.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: zkabelac at sourceware.org 2011-01-28 16:01:32
Modified files:
libdm/mm : dbg_malloc.c
Log message:
Compile code for memory debuging only with DEBUG_MEM
When it's not in use - do not compile this code.
Improves lcov code coverage results for this code a lot :)
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/libdm/mm/dbg_malloc.c.diff?cvsroot=lvm2&r1=1.21&r2=1.22
--- LVM2/libdm/mm/dbg_malloc.c 2010/09/30 21:06:52 1.21
+++ LVM2/libdm/mm/dbg_malloc.c 2011/01/28 16:01:32 1.22
@@ -15,6 +15,8 @@
#include "dmlib.h"
+#ifdef DEBUG_MEM
+
#include <assert.h>
#include <stdarg.h>
@@ -249,6 +251,8 @@
}
}
+#endif
+
void *dm_malloc_aux(size_t s, const char *file __attribute__((unused)),
int line __attribute__((unused)))
{
next reply other threads:[~2011-01-28 16:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 16:01 zkabelac [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-02-08 15:52 LVM2/libdm/mm dbg_malloc.c zkabelac
2011-10-28 20:37 zkabelac
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=20110128160132.23140.qmail@sourceware.org \
--to=zkabelac@sourceware.org \
--cc=lvm-devel@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.