curl/tests/data/test96

<testcase>
<info>
<keywords>
TrackMemory
</keywords>
</info>

#
# Server-side
<reply>
</reply>

# Client-side
<client>
<server>
none
</server>
<features>
TrackMemory
</features>

<name>
curl memory tracking operational
</name>
<command>
--version
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
<file name="log/memdump">
MEM tool_paramhlp.c
MEM tool_cfgable.c
MEM tool_cfgable.c
MEM tool_cfgable.c
</file>
<stripfile>
$_ = '' if ((($_ !~ /tool_paramhlp/) && ($_ !~ /tool_cfgable/)) || ($_ =~ /free\(\(nil\)\)/))
s/:\d+.*//
s:^(MEM )(.*/)(.*):$1$3:
</stripfile>
</verify>

</testcase>
tests: add #96 #558 and #1330 These verfy that the 'memory tracking' subsystem is actually doing its job when using curl tool (#96), a test in libtest (#558) and also a unit test (#1330), in order to prevent regressions in this functionallity. 2013-03-15 14:58:00 -04:00			`<testcase>`
			`<info>`
			`<keywords>`
			`TrackMemory`
			`</keywords>`
			`</info>`

			`#`
			`# Server-side`
			`<reply>`
			`</reply>`

			`# Client-side`
			`<client>`
			`<server>`
			`none`
			`</server>`
			`<features>`
			`TrackMemory`
			`</features>`

			`<name>`
			`curl memory tracking operational`
			`</name>`
			`<command>`
			`--version`
			`</command>`
			`</client>`

			`#`
			`# Verify data after the test has been "shot"`
			`<verify>`
test suite: stop conversion of valid output to CRLF on Windows Since the output isn't actually being written in text-mode and it was rather used as a workaround, disable text-mode for these tests. 2014-02-01 07:49:58 -05:00			`<file name="log/memdump">`
tests: 96, 558, 1330: strip build subdirectory dependent leading path 2013-03-15 19:59:17 -04:00			`MEM tool_paramhlp.c`
			`MEM tool_cfgable.c`
test96: updated according to recent changes 2014-02-08 17:20:10 -05:00			`MEM tool_cfgable.c`
			`MEM tool_cfgable.c`
tests: add #96 #558 and #1330 These verfy that the 'memory tracking' subsystem is actually doing its job when using curl tool (#96), a test in libtest (#558) and also a unit test (#1330), in order to prevent regressions in this functionallity. 2013-03-15 14:58:00 -04:00			`</file>`
			`<stripfile>`
free: instead of Curl_safefree() Since we just started make use of free(NULL) in order to simplify code, this change takes it a step further and: - converts lots of Curl_safefree() calls to good old free() - makes Curl_safefree() not check the pointer before free() The (new) rule of thumb is: if you really want a function call that frees a pointer and then assigns it to NULL, then use Curl_safefree(). But we will prefer just using free() from now on. 2015-03-16 10:01:15 -04:00			`$_ = '' if ((($_ !~ /tool_paramhlp/) && ($_ !~ /tool_cfgable/)) \|\| ($_ =~ /free\(\(nil\)\)/))`
tests: add #96 #558 and #1330 These verfy that the 'memory tracking' subsystem is actually doing its job when using curl tool (#96), a test in libtest (#558) and also a unit test (#1330), in order to prevent regressions in this functionallity. 2013-03-15 14:58:00 -04:00			`s/:\d+.*//`
tests: 96, 558, 1330: strip build subdirectory dependent leading path 2013-03-15 19:59:17 -04:00			`s:^(MEM )(./)(.):$1$3:`
tests: add #96 #558 and #1330 These verfy that the 'memory tracking' subsystem is actually doing its job when using curl tool (#96), a test in libtest (#558) and also a unit test (#1330), in order to prevent regressions in this functionallity. 2013-03-15 14:58:00 -04:00			`</stripfile>`
			`</verify>`

			`</testcase>`