Age | Commit message (Collapse) | Author |
|
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.
|
|
|
|
|
|
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.
|
|
|
|
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.
|
|
we seem to have nailed that one now!
|
|
|
|
in the failure frequency
|
|
response with a size 5 instead of size 0, to see if this has an impact on
the failure frequency - test 91 still fails occationally.
|