curl/tests/data/test558

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

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

# Client-side
<client>
<server>
none
</server>
<features>
TrackMemory
ipv6
</features>
# tool is what to use instead of 'curl'
<tool>
lib558
</tool>

<name>
libtest memory tracking operational
</name>
<command>
nothing
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
<file name="log/memdump">
MEM lib558.c: malloc()
MEM lib558.c: free()
MEM dynbuf.c: realloc()
MEM dynbuf.c: realloc()
MEM escape.c: free()
</file>
<stripfile>
s/^MEM escape.c:\d+ free\(\(nil\)\)[\n]$//
s/ =.*//
s/\(.*\)/()/
s/:\d+/:/
s:^(MEM |FD )(.*/)(.*):$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-15 14:58:00 -04:00			`<testcase>`
			`<info>`
			`<keywords>`
			`TrackMemory`
			`</keywords>`
			`</info>`

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

			`# Client-side`
			`<client>`
			`<server>`
			`none`
			`</server>`
			`<features>`
			`TrackMemory`
test558: updated after ipv6-check move Follow-up commit to c50980807c5 to make this test pass. 2016-07-20 17:04:06 -04:00			`ipv6`
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			`</features>`
			`# tool is what to use instead of 'curl'`
			`<tool>`
			`lib558`
			`</tool>`

			`<name>`
			`libtest memory tracking operational`
			`</name>`
			`<command>`
			`nothing`
			`</command>`
			`</client>`

			`#`
			`# Verify data after the test has been "shot"`
			`<verify>`
testsuite: use binary output mode for custom curl test tools Do not try to convert line-endings to CRLF on Windows by setting stdout to binary mode, just like the curl tool does if --ascii is not specified. This should prevent corrupted stdout line-ending output like CRCRLF. In order to make the previously naive text-aware tests work with binary mode on Windows, text-mode is disabled for them if it is not actually part of the test case and line-endings are corrected. 2014-01-31 18:58: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 lib558.c: malloc()`
			`MEM lib558.c: free()`
curl: use curlx_dynbuf for realloc when loading config files ... fixes an integer overflow at the same time. Reported-by: ihsinme on github Assisted-by: Jay Satiro Closes #5946 2020-09-09 09:41:25 -04:00			`MEM dynbuf.c: realloc()`
			`MEM dynbuf.c: realloc()`
tests: 96, 558, 1330: strip build subdirectory dependent leading path 2013-03-15 19:59:17 -04:00			`MEM escape.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-15 14:58:00 -04:00			`</file>`
			`<stripfile>`
test558: fix for multissl builds vtls.c:multissl_init() might do a curl_free() call so strip that out to make this work with more builds. We just want to verify that memorytracking works so skipping one line is no harm. 2018-01-18 16:17:05 -05:00			`s/^MEM escape.c:\d+ free\(\(nil\)\)[\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-15 14:58:00 -04:00			`s/ =.*//`
			`s/\(.*\)/()/`
			`s/:\d+/:/`
test558: fix test by stripping file paths from FD lines 2016-07-21 11:06:04 -04:00			`s:^(MEM \|FD )(./)(.):$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 05:11:50 -05: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 09:41:49 -04: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-15 14:58:00 -04:00			`</stripfile>`
			`</verify>`

			`</testcase>`