Home
last modified time | relevance | path

Searched refs:thread (Results 1 – 25 of 33) sorted by relevance

12

/curl/docs/libcurl/
H A Dlibcurl-thread.md4 Title: libcurl-thread
16 libcurl-thread - libcurl thread safety
20 libcurl is thread safe but has no internal thread synchronization. You may have
28 than one thread at any given time.
36 Note that some items are specifically documented as not thread-safe in the
41 All current TLS libraries libcurl supports are thread-safe.
52 OpenSSL thread cleanup.
82 the former signal handler while another thread should still ignore it.
90 safe. Some operating systems are known to have faulty thread
98 These functions are thread-safe since libcurl 7.84.0 if
[all …]
H A Dcurl_global_cleanup.md10 - libcurl-thread (3)
35 This function is thread-safe since libcurl 7.84.0 if
39 If this is not thread-safe, you must not call this function when any other
40 thread in the program (i.e. a thread sharing the same memory) is running.
41 This does not just mean no other thread that is using libcurl. Because
43 similarly thread unsafe, it could conflict with any other thread that uses
61 OpenSSL thread cleanup. Refer to libcurl-thread(3).
H A Dcurl_global_init.md48 This function is thread-safe on most platforms. Then curl_version_info(3) has
51 If this is not thread-safe (the bit mentioned above is not set), you must not
52 call this function when any other thread in the program (i.e. a thread sharing
53 the same memory) is running. This does not just mean no other thread that is
55 that are similarly thread unsafe, it could conflict with any other thread that
H A Dcurl_multi_wakeup.md29 This function can be called from any thread and it wakes up a sleeping
60 /* this is thread 1 */
79 /* this is thread 2 */
H A Dcurl_global_trace.md39 This function is thread-safe since libcurl 8.3.0 if curl_version_info(3) has
42 If this is not thread-safe, you must not call this function when any other
43 thread in the program (i.e. a thread sharing the same memory) is running. This
44 does not just mean no other thread that is using libcurl. Because
46 thread unsafe, it could conflict with any other thread that uses these other
H A Dlibcurl.md11 - libcurl-thread (3)
54 thread. See further details in the libcurl-multi(3) man page.
132 libcurl is thread safe but there are a few exceptions. Refer to
133 libcurl-thread(3) for more information.
175 The global constant functions are thread-safe since libcurl 7.84.0 if
177 (most platforms). Read libcurl-thread(3) for thread safety guidelines.
179 If the global constant functions are *not thread safe*, then you must
180 not call them when any other thread in the program is running. It
181 is not good enough that no other thread is using libcurl at the time,
183 libraries, and those functions are similarly thread-unsafe. You cannot
[all …]
H A Dcurl_global_sslset.md59 This function is thread-safe since libcurl 7.84.0 if
63 If this is not thread-safe, you must not call this function when any other
64 thread in the program (i.e. a thread sharing the same memory) is running.
65 This does not just mean no other thread that is using libcurl.
H A Dcurl_global_init_mem.md39 threaded resolver option then the callback functions must be thread safe. The
41 default) so we strongly urge you to make your callback functions thread safe.
H A DMakefile.inc121 libcurl-thread.3 \
H A Dcurl_easy_init.md47 cases for platforms where curl_global_init(3) is not thread-safe, and it may
H A Dlibcurl-share.md51 internal thread synchronization, you must provide mutex callbacks if you are
H A Dcurl_version_info.md42 curl_global_init(3) has not been called. It is therefore not thread-safe
316 libcurl was built with thread-safety support (Atomic or SRWLOCK) to protect
317 curl initialization. (Added in 7.84.0) See libcurl-thread(3)
H A Dcurl_multi_poll.md51 The curl_multi_wakeup(3) function can be used from another thread to
H A Dcurl_easy_pause.md42 function from another thread. To unpause, you may for example call it from the
/curl/tests/data/
H A Dtest30265 thread-safe
28 curl_global_init thread-safety
H A Dtest156534 wakeup from another thread
/curl/tests/libtest/
H A Dlib3207.c148 curl_thread_t thread[THREAD_SIZE]; in execute() local
158 thread[i] = Curl_thread_create(test_thread, (void *)&ctx[i]); in execute()
161 if(thread[i]) { in execute()
162 Curl_thread_join(&thread[i]); in execute()
163 Curl_thread_destroy(thread[i]); in execute()
/curl/docs/libcurl/opts/
H A DCURLOPT_DNS_USE_GLOBAL_CACHE.md34 thread-safe and this uses a global variable.
54 /* switch off the use of a global, thread unsafe, cache */
H A DCURLOPT_QUICK_EXIT.md34 canceling and/or forgetting about a resolver thread, at the expense of a
/curl/tests/server/
H A Dsockfilt.c601 curl_win_thread_handle_t thread; in select_ws_wait() local
612 thread = CreateThread(NULL, 0, &select_ws_wait_thread, data, 0, NULL); in select_ws_wait()
614 thread = _beginthreadex(NULL, 0, &select_ws_wait_thread, data, 0, NULL); in select_ws_wait()
618 if(!thread) { in select_ws_wait()
621 return (HANDLE)thread; in select_ws_wait()
631 HANDLE thread; /* internal thread handle (indexed by nth) */ member
728 data[nth].thread = handle; in select_ws()
782 data[nth].thread = handle; in select_ws()
812 WaitForSingleObjectEx(data[i].thread, INFINITE, FALSE); in select_ws()
813 CloseHandle(data[i].thread); in select_ws()
H A Dutil.c764 curl_win_thread_handle_t thread; in install_signal_handlers() local
766 thread = CreateThread(NULL, 0, &main_window_loop, in install_signal_handlers()
769 thread = _beginthreadex(NULL, 0, &main_window_loop, in install_signal_handlers()
772 thread_main_window = (HANDLE)thread; in install_signal_handlers()
/curl/docs/examples/
H A DMakefile.inc154 smooth-gtk-thread.c \
/curl/.github/workflows/
H A Dlinux.yml189 - name: thread-sanitizer
194 CFLAGS="-fsanitize=thread -g"
195 LDFLAGS="-fsanitize=thread -Wl,-rpath,$HOME/openssl3/lib"
377 …CC="clang" CFLAGS="-fsanitize=thread" LDFLAGS="-fsanitize=thread" ./config --prefix=$HOME/openssl3…
/curl/lib/
H A DMakefile.inc109 asyn-thread.c \
/curl/docs/
H A DFAQ84 5.1 Is libcurl thread-safe?
153 libcurl is free, thread-safe, IPv6 compatible, feature rich, well
1121 5.1 Is libcurl thread-safe?
1126 programs. libcurl will use thread-safe functions instead of non-safe ones if
1130 There may be some exceptions to thread safety depending on how libcurl was
1131 built. Please review the guidelines for thread safety to learn more:
1312 can call from another thread or similar that will stop it immediately.
1400 Put simply: no, libcurl will execute in the same thread you call it in. All
1401 callbacks will be called in the same thread as the one you call libcurl in.
1403 If you want to avoid your thread to be blocked by the libcurl call, you make
[all …]

Completed in 44 milliseconds

12