aboutsummaryrefslogtreecommitdiff
path: root/tests/valgrind.supp
AgeCommit message (Collapse)Author
2014-03-15valgrind.supp: added another test 165 suppressionDan Fandrich
This one seems to come and go as the optimizer decides how best to inline some functions.
2014-02-26valgrind.supp: tweaked a test 165 suppressionDan Fandrich
A recent change seems to have slightly changed the call stack produced by the gcc optimizer.
2014-02-15valgrind: added another test 165 suppressionDan Fandrich
This one is needed with the gcc options -fstack-protector-all -O2 That brings the number of suppressions for test 165 to four, and I suspect I could find another two missing without trying very hard. I'm beginning to think suppressions isn't the best way to handle these kinds of cases.
2014-02-14valgrind: added suppression on optimized codeDan Fandrich
gcc 4.7.2 with -O2 will optimize Curl_connect by inlining some functions two levels deep, which makes the valgrind suppression fail to match. The underlying reason for these idna suppressions is a gcc strlen optimization when compiling libidn; compiling it with -fno-builtin-strlen makes this suppression unnecessary.
2014-02-05valgrind: updated suppressions fileDaniel Stenberg
The call stack was modified in 2dc7ad23 so the supressions didn't work anymore.
2013-08-28valgrind.supp: fix for regular curl_easy_perform tooDaniel Stenberg
When we introduced curl_easy_perform_ev, this got a slightly modified call trace. Without this, test 165 causes a false positive valgrind error.
2013-08-28valgrind.supp: add the event-based call stack-trace tooDaniel Stenberg
Without this, test 165 triggers a valgrind error when ran with curl_easy_perform_ev
2013-01-17always-multi: always use non-blocking internalsDaniel Stenberg
Remove internal separated behavior of the easy vs multi intercace. curl_easy_perform() is now using the multi interface itself. Several minor multi interface quirks and bugs have been fixed in the process. Much help with debugging this has been provided by: Yang Tse