Ensure progress.size_dl/progress.size_ul are always >= 0
Historically the default "unknown" value for progress.size_dl and progress.size_ul has been zero, since these values are initialized implicitly by the calloc that allocates the curl handle that these variables are a part of. Users of curl that install progress callbacks may expect these values to always be >= 0. Currently it is possible for progress.size_dl and progress.size_ul to by set to a value of -1, if Curl_pgrsSetDownloadSize() or Curl_pgrsSetUploadSize() are passed a "size" of -1 (which a few places currently do, and a following patch will add more). So lets update Curl_pgrsSetDownloadSize() and Curl_pgrsSetUploadSize() so they make sure that these variables always contain a value that is >= 0. Updates test579 and test599. Signed-off-by: Brandon Casey <drafnel@gmail.com>
This commit is contained in:
committed by
Daniel Stenberg
parent
8acbb074f8
commit
6beb0eeea1
@@ -77,12 +77,11 @@ http://%HOSTIP:%HTTPPORT/579 log/ip579
|
||||
<verify>
|
||||
<file name="log/ip579">
|
||||
Progress callback called with UL 0 out of 0
|
||||
Progress callback called with UL 0 out of -1
|
||||
Progress callback called with UL 8 out of -1
|
||||
Progress callback called with UL 16 out of -1
|
||||
Progress callback called with UL 26 out of -1
|
||||
Progress callback called with UL 61 out of -1
|
||||
Progress callback called with UL 66 out of -1
|
||||
Progress callback called with UL 8 out of 0
|
||||
Progress callback called with UL 16 out of 0
|
||||
Progress callback called with UL 26 out of 0
|
||||
Progress callback called with UL 61 out of 0
|
||||
Progress callback called with UL 66 out of 0
|
||||
</file>
|
||||
</verify>
|
||||
</testcase>
|
||||
|
||||
Reference in New Issue
Block a user