summaryrefslogtreecommitdiff
path: root/tests/data/test1132
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2012-11-17 00:59:42 +0100
committerDaniel Stenberg <daniel@haxx.se>2012-11-17 13:56:38 +0100
commitee588fe088077785d9ad9263e03e1e525b074261 (patch)
tree85aea44bd6e3354311ac0c60577c2d8bacf45445 /tests/data/test1132
parentdb4215f14a9ee2aca01315fa8cf100915284b15d (diff)
downloadcurl-ee588fe088077785d9ad9263e03e1e525b074261.tar.gz
mem-include-scan: verify memory #includes
If we use memory functions (malloc, free, strdup etc) in C sources in libcurl and we fail to include curl_memory.h or memdebug.h we either fail to properly support user-provided memory callbacks or the memory leak system of the test suite fails. After Ajit's report of a failure in the first category in http_proxy.c, I spotted a few in the second category as well. These problems are now tested for by test 1132 which runs a perl program that scans for and attempts to check that we use the correct include files if a memory related function is used in the source code. Reported by: Ajit Dhumale Bug: http://curl.haxx.se/mail/lib-2012-11/0125.html
Diffstat (limited to 'tests/data/test1132')
-rw-r--r--tests/data/test113224
1 files changed, 24 insertions, 0 deletions
diff --git a/tests/data/test1132 b/tests/data/test1132
new file mode 100644
index 000000000..366ffc77c
--- /dev/null
+++ b/tests/data/test1132
@@ -0,0 +1,24 @@
+<testcase>
+<info>
+<keywords>
+memory-includes
+</keywords>
+</info>
+
+#
+# Client-side
+<client>
+<server>
+none
+</server>
+
+ <name>
+Verify memory #include files in libcurl's C source files
+ </name>
+
+<command type="perl">
+%SRCDIR/mem-include-scan.pl %SRCDIR/../lib
+</command>
+</client>
+
+</testcase>