[PATCH] [Bug #21705] Fix segfaults on Windows

	It should check the type of the argument and coercion before
	converting the encoding.

	[Bug #21497] [ruby/socket]: add full prototype
	MIME-Version: 1.0
	Content-Type: text/plain; charset=UTF-8
	Content-Transfer-Encoding: 8bit

	otherwise, gcc 15 will complain:

	> init.c:573:19: error: too many arguments to function ‘Rconnect’; expected 0, have 3
	>   573 |     return (VALUE)Rconnect(arg->fd, arg->sockaddr, arg->len);
	>       |                   ^~~~~~~~ ~~~~~~~
	> In file included from init.c:11:
	> rubysocket.h:294:5: note: declared here
	>   294 | int Rconnect();
	>       |     ^~~~~~~~

	> sockssocket.c:33:9: error: too many arguments to function ‘SOCKSinit’; expected 0, have 1
	>    33 |         SOCKSinit("ruby");
	>       |         ^~~~~~~~~ ~~~~~~
	> In file included from sockssocket.c:11:
	> rubysocket.h:293:6: note: declared here
	>   293 | void SOCKSinit();
	>       |      ^~~~~~~~~

	Signed-off-by: Z. Liu <zhixu.liu@gmail.com>

When the registerred unblock function is called, it should retry
the cancelled blocking function if possible after checkints.

For example, `SIGCHLD` can cancel this method, but it should not
raise any exception if there is no trap handlers.

The following is repro-code:

```ruby
require 'socket'
PN = 10_000

1000000.times{
  p _1
  PN.times{
    fork{
      sleep rand(0.3)
    }
  }
  i = 0
  while i<PN
    cpid = Process.wait -1, Process::WNOHANG
    if cpid
      # p [i, cpid]
      i += 1
    end

    begin
      TCPServer.new(nil, 0).close
    rescue
      p $!
      exit!
    end
  end
}
```

	[Bug #20592] Fix segfault when sending NULL to freeaddrinfo

	On alpine freeaddrinfo does not accept NULL pointer

	Fix dangling `else`

Revert "Set AI_ADDRCONFIG when making getaddrinfo(3) calls for outgoing conns"

This reverts commit 673ed41c81cf5a6951bcb2c3dec82d7bd6ea7440.

Make sure the correct error is raised for EAI_SYSTEM resolver fail

	In case of EAI_SYSTEM, getaddrinfo is supposed to set more detail in
	errno; however, because we call getaddrinfo on a thread now, and errno
	is threadlocal, that information is being lost. Instead, we just raise
	whatever errno happens to be on the calling thread (which can be
	something very confusing, like `ECHILD`).

	Fix it by explicitly propagating errno back to the calling thread
	through the getaddrinfo_arg structure.

	[Bug #20198]
	---
	 ext/socket/raddrinfo.c | 25 +++++++++++++++++++------
	 1 file changed, 19 insertions(+), 6 deletions(-)

Remove setaffinity of pthread for getaddrinfo

	It looks like `sched_getcpu(3)` returns a strange number on some
	(virtual?) environments.

	I decided to remove the setaffinity mechanism because the performance
	does not appear to degrade on a quick benchmark even if removed.

	[Bug #20172]
	---
	 ext/socket/extconf.rb  |  2 --
	 ext/socket/raddrinfo.c | 48 ++++--------------------------------------------
	 2 files changed, 4 insertions(+), 46 deletions(-)

	Free pthread_attr after setting up the thread

	[bug #20149]
	---
	 ext/socket/raddrinfo.c | 12 +++++++++++-
	 1 file changed, 11 insertions(+), 1 deletion(-)

Ref: https://github.com/ruby/ruby/pull/6407

[Bug #19012]

`0` is now interpreted as closed connection an not an
empty packet, as these are very rare and pretty much
useless.