summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
Diffstat (limited to 'dev-util/ccmalloc/metadata.xml')
-rw-r--r--dev-util/ccmalloc/metadata.xml13
1 files changed, 0 insertions, 13 deletions
diff --git a/dev-util/ccmalloc/metadata.xml b/dev-util/ccmalloc/metadata.xml
deleted file mode 100644
index 0cfe76fd8db1..000000000000
--- a/dev-util/ccmalloc/metadata.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
-<pkgmetadata>
- <!-- maintainer-needed -->
- <longdescription lang="en">
- If you want to remove memory leaks from your C or C++ programs or you
- experience strange bugs, probably due to pointer access to freed data,
- then ccmalloc may be the right tool for you. In general it can help you
- to track down memory related problems with C and C++ programs. It does
- not replace more sophistacted tools such as purify or valgrind, since it
- can not detect illegal memory reads, at least not all type of memory reads.
- </longdescription>
-</pkgmetadata>