On Thu, Sep 21, 2023 at 12:08:33PM -0400, Anass Meskini via curl-library wrote:
> Thanks Dan for the clarification.
> I think it might be worth mentioning in the doc that this function might
> create
> a thread.
It is called the "threaded resolver" after all, and that name is found in 8
On Thu, Sep 21, 2023 at 1:09 PM Anass Meskini via curl-library <
curl-library@lists.haxx.se> wrote:
> Thanks Dan for the clarification.
> I think it might be worth mentioning in the doc that this function might
> create a thread.
> Would setting CURLOPT_RESOLVE result in curl_multi_perform never
Thanks Dan for the clarification.
I think it might be worth mentioning in the doc that this function might
create a thread.
Would setting CURLOPT_RESOLVE result in curl_multi_perform never creating a
new thread?
Also when I run multi-app.c in helgrind, I see:
> ==339231==
On Wed, Sep 20, 2023 at 09:11:32PM -0400, Anass Meskini via curl-library wrote:
> I compiled curl from the github repository with --with-openssl then I compiled
> multi-app.c.
> When I run the program in gdb and add a breakpoint for pthread_create I see:
curl will use the threaded resolver option
Hello,
I compiled curl from the github repository with --with-openssl then I
compiled multi-app.c.
When I run the program in gdb and add a breakpoint for pthread_create I see:
> gdb) bt
> #0 __pthread_create_2_1 (newthread=0x55590d50, attr=0x0,
> start_routine=0x77f61d20,
