Skip to content

340bb19 breaks intended usage of curl_multi_assign #8480

@m6w6

Description

@m6w6

I did this

Watched CI break with curl 7.81.

Seriously, 340bb19 breaks the intended usage of curl_multi_assign.

Quoting docs:

In a typical application you allocate a struct or at least use some kind of semi-dynamic data for each socket that we must wait for action on when using the curl_multi_socket_action approach.

When our socket-callback gets called by libcurl and we get to know about yet another socket to wait for, we can use curl_multi_assign to point out the particular data so that when we get updates about this same socket again, we do not have to find the struct associated with this socket by ourselves.

I expected the following

curl_multi_assign to work from within callbacks.

Coincidentally, docs/examples/hiperfifo.c and docs/examples/multi-event.c are broken, too.

curl/libcurl version

7.81/master

operating system

POSIX

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions