curl/tests/data/test1330

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

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

# Client-side
<client>
<server>
none
</server>
<features>
unittest
TrackMemory
</features>
<name>
unit tests memory tracking operational
</name>
<command>
nothing
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
<file name="log/memdump">
MEM unit%TESTNUMBER.c: malloc()
MEM unit%TESTNUMBER.c: free()
</file>
<stripfile>
s/ =.*//
s/\(.*\)/()/
s/:\d+/:/
s:^(MEM )(.*/)(.*):$1$3:
s/\r\n/\n/
s/^MEM getenv.c: realloc\(\)[\n]$//
s/^MEM getenv.c: free\(\)[\n]$//
</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-16 02:58:00 +08:00			`<testcase>`
			`<info>`
			`<keywords>`
			`unittest`
			`TrackMemory`
			`</keywords>`
			`</info>`

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

			`# Client-side`
			`<client>`
			`<server>`
			`none`
			`</server>`
			`<features>`
			`unittest`
			`TrackMemory`
			`</features>`
			`<name>`
			`unit tests memory tracking operational`
			`</name>`
			`<command>`
			`nothing`
			`</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 20:49:58 +08:00			`<file name="log/memdump">`
tests: use %TESTNUMBER instead of fixed number This makes the tests easier to copy and relocate to other test numbers without having to update content. Closes #6738 2021-03-13 00:38:26 +08:00			`MEM unit%TESTNUMBER.c: malloc()`
			`MEM unit%TESTNUMBER.c: free()`
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-16 02:58:00 +08:00			`</file>`
			`<stripfile>`
			`s/ =.*//`
			`s/\(.*\)/()/`
			`s/:\d+/:/`
tests: 96, 558, 1330: strip build subdirectory dependent leading path 2013-03-16 07:59:17 +08:00			`s:^(MEM )(./)(.):$1$3:`
TrackMemory tests: always remove CR before LF It was removed for output containing ' =' via `s/ =.*//`. With classic MinGW, this made lines with `free()` end with CRLF, but lines with e.g. `malloc()` end with only LF. The tests expect LF only. Closes https://github.com/curl/curl/pull/4788 2020-01-06 18:11:50 +08:00			`s/\r\n/\n/`
TrackMemory tests: ignore realloc and free in getenv.c These are only called for WIN32. Closes https://github.com/curl/curl/pull/5767 2020-08-02 21:41:49 +08:00			`s/^MEM getenv.c: realloc\(\)[\n]$//`
			`s/^MEM getenv.c: free\(\)[\n]$//`
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-16 02:58:00 +08:00			`</stripfile>`
			`</verify>`
			`</testcase>`