BSD sockets API explained

[@zianwar_]

Hi Sergey, I appreciate you sharing your knowledge, this content is so good! 1. You give useful historical context; I never knew why the "select" system call exists until now :) 2. You tend to simplify in your explanation and programs which is so delightful.

[@mongoose-networking-library]

You are welcome!

[@StevenHokins]

Very nice, thank you

[@shefiroth12]

finished the vid, very useful. thanks

[@КонстантинАнтипов-д3о]

After closing any socket connection program finishes with an error: "Segmentation fault (core dumped)", what can be the reason why it happens?

[@mongoose-networking-library]

Please respond to the gist with details on your environment, and how to reproduce it!

[@КонстантинАнтипов-д3о]

​@@mongoose-networking-library I'm using Oracle VM with Ubuntu 24.04 LTS on it. Trying to make tcp communication service for embedded stm32 device, but testing program currently on Ubuntu first. So when I compiling example, that was showed in the video, there are no errors, but when I testing compiled app with netcat or "curl" command it response with current date and time, but slightly after socket close operation, receiving "Segmentation fault (core dumped)" error and app automatically closing (dropping every other connections) and I need to restart it. btw, tested it on my embedded stm32 linux device and got same error.

[@КонстантинАнтипов-д3о]

I'm using Oracle VM with Ubuntu 24.04 LTS on it. Making tcp communication service for embedded stm32 device, but testing program currently on Ubuntu first. So when I compiling example, that was showed in the video, there are no errors, but when I testing compiled app with netcat or "curl" command it response with current date and time, but slightly after socket close operation, receiving "Segmentation fault (core dumped)" error and app automatically closing (dropping every other connections) and I need to restart it. btw, tested it on my embedded stm32 linux device and got same error. UPD: this issue fixes by deleting: "free(c);" at close function, but I think it will cause memory troubles later, maybe there is better way to solve it.

[@КонстантинАнтипов-д3о]

UPD#2: fixed it by replacing in add_connection() function "calloc" of conn *c by this: struct conn *c; c = (struct conn *) calloc(1, sizeof(struct conn)); Now "free(c);" function working properly and do not crushes my app.

[@mongoose-networking-library]

@@КонстантинАнтипов-д3о Thank you! Yes, there was a bug in the connection deletion - gist updated, please confirm!

[@TheMadProgrammersOfficial]

how does this not have a million views? only 549 i mean come on

[@mongoose-networking-library]

Share it with your colleagues :)