@xxpertHacker thought line 50 was the problem since removing it stopped the seg faults.

But just realized I wrote realloc instead of calloc :|

@xxpertHacker I am writing nonsense :D

@xxpertHacker wow great putting it in a struct leads to another seg fault :|

typedef struct Server {
	int PORT;

	int* clients;
	size_t client_t;
	int MAX_CLIENTS;

	int master_sd;
	
	fd_set readfds;
	struct sockaddr_in address;
} Server_;

@realTronsi yay, go make another question so I could easily get 5 more useless internet points, lol

@xxpertHacker just answer it in 5 different comments :D

@realTronsi Then I'll want 25 useless internet points.

@xxpertHacker that makes no sense, just answer :(

@xxpertHacker okay answer word by word so you get #word free internet points

@realTronsi did you mean to call calloc(server.client_t?

Go add this too:

CC = clang
CFLAGS = -Wall -pedantic

@xxpertHacker wdym i'm not callocing the client_t

@realTronsi Yes, that's the point.

This is bad code:

int* clients;
clients = calloc(clients, *clients);

It literally makes no sense, and it's a type error.
And it's undefined behavior.

Look at GCC's pedantic warning:

server/server.c: In function ‘create_server’:
server/server.c:35:26: warning: passing argument 1 of ‘calloc’ makes integer from pointer without a cast [-Wint-conversion]
  server.clients = calloc(server.clients, (server.client_t)*sizeof(*server.clients));
                          ^~~~~~

Simply put, that is a type error.

Next,

In file included from server/../include/server.h:5:0,
                 from server/server.c:1:
/usr/include/stdlib.h:541:14: note: expected ‘size_t {aka long unsigned int}’ but argument is of type ‘int *’
 extern void *calloc (size_t __nmemb, size_t __size)
              ^~~~~~

You're passing the address of a pointer, which is currently initialized by random memory, as a size_t.

For all you know, you're doing calloc(0x3434238935, ...).

(btw, use a code formatter)

wait wtf lmao yeah I see

server.clients = calloc(1, (server.client_t)*sizeof(*server.clients));

idek why I put the address there, when I wrote this 2 days ago I must've been thinking of realloc and thought I calloced b4

@realTronsi omg, finally you see why I saw that code as nonsense.

Also, this is why I dislike weakly-typed languages, noobs run into errors too often, and implicit casts even screw me over.

@xxpertHacker

noobs run into errors too often

._.

idk what happened for this one but I'm not normally this autistic

@programmeruser by clicking the run button?

@realTronsi no, gdb main.o then run

@realTronsi and here's the backtrace:

#0  __GI___libc_realloc (bytes=4, oldmem=0x3) at malloc.c:3165
#1  realloc_hook_ini (ptr=0x3, sz=4, caller=<optimized out>) at hooks.c:41
#2  0x000056441c0c9972 in create_server (PORT=80) at server/server.c:35
#3  0x000056441c0c97fb in main () at examples/main.c:9

@programmeruser doesn't really tell me much

@programmeruser He's calling realloc on a bad pointer, https://repl.it/talk/ask/Im-getting-a-realloc-abortion-but-I-do/87284/397310.