Home
last modified time | relevance | path

Searched refs:memory (Results 76 – 88 of 88) sorted by relevance

1234

/curl/docs/libcurl/
H A Dlibcurl-errors.md174 A memory allocation request failed. This is serious badness and
587 Not enough memory was available.
630 A memory function failed.
H A Dcurl_easy_getinfo.md33 You should not free the memory returned by this function unless it is
H A Dlibcurl-security.md464 # Secrets in memory
468 in memory. In many cases they are stored in the heap for as long as the handle
475 needed, libcurl does not explicitly clear memory before freeing it, so
H A Dcurl_version_info.md329 libcurl was built with memory tracking debug capabilities. This is mainly of
H A Dcurl_mprintf.md68 output string as pointer to a newly allocated memory area. The returned string
H A Dlibcurl-tutorial.md521 There are three possible data sources for a part: memory using
1189 memory and used properly in subsequent requests when the same handle is
/curl/docs/libcurl/opts/
H A DCURLOPT_SSL_CTX_FUNCTION.md102 /* use it to read the PEM formatted certificate from memory into an
/curl/packages/vms/
H A Dcurlmsg.msg75 OUT_OF_MEMORY <out of memory>
/curl/docs/cmdline-opts/
H A Dform.md39 buffered in memory first by curl to determine its size and allow a possible
/curl/docs/
H A DTODO119 13.7 Less memory massaging with Schannel
423 Introducing a concept and system to erase secrets from memory after use, it
838 13.7 Less memory massaging with Schannel
840 The Schannel backend does a lot of custom memory management we would rather
841 avoid: the repeated alloc + free in sends and the custom memory + realloc
1278 renders the exploitation of memory corruption vulnerabilities a lot more
1283 overwrite memory. A few tests showed that enabling these features had close
H A DFAQ85 5.2 How can I receive all data into a large memory chunk?
1134 5.2 How can I receive all data into a large memory chunk?
1149 char *memory;
1160 mem->memory = (char *)realloc(mem->memory, mem->size + realsize + 1);
1161 if (mem->memory) {
1162 memcpy(&(mem->memory[mem->size]), ptr, realsize);
1164 mem->memory[mem->size] = 0;
1185 each others' variable memory areas). If you set CURLOPT_WRITEDATA you must
H A DKNOWN_BUGS558 error that says "no memory" !
/curl/m4/
H A Dcurl-compilers.m41255 dnl Actually the curl debug memory tracking feature can
1285 AC_MSG_CHECKING([if curl debug memory tracking can be enabled])
1289 AC_MSG_WARN([cannot enable curl debug memory tracking.])

Completed in 46 milliseconds

1234