The problem lies in the fact that the function only prints the header of the request and the custom string. The body doesn't print even though it should, I think it's all caused by the /0 string terminator, can you help me? I've checked all the variable sizes and they match with wireshark so I'm assuming it's not a calculation related issue

btu looking into your example Content-Length: 0 looks like there is no body to print

however i have been using wireshark using post requests and the content is not displaying anyway, i have no problem with requests without body, they print fine. requests with a body are the problem, because the body doesn't get printed

what about the debugger?

Yeah i know... I havent it im only gcc for compilation, did u have any advice

like this one ? https://onlinegdb.com/cdHVWXjmT

because I already commented out the line which was terminating your string at length of your headers by null characters

I had tried this solution, but unfortunately by doing so the printing is bad and unreadable characters appear, do you think it is because I have to add a string terminator at the end of the body? Thanks again

print your inputs before funvtion is called

or to be more correct - any 0 byte will break it

I guys. I have a Client - Server application. This simulates (via UDP socket) the Go-Back-N protocol, so you give a window dimension and it will simulate go back n. The code (both Client and Server) works and does what it is meant to do. The only problem lies in a segmentation fault client-side taking place when I remove fprintf server-side. Being the biggest challenge, I had to use several fprintf to debug the server. And, as long as those fprintf stay there it's all safe and sound, but the very moment I delete them, client will crash after having recieved some packets. I don't know why it happens, but I had more experienced people check my code and there are no bad accesses nor errors with pointers or malloc. So I don't really know what's happening. As I said, the code has got no formal error. What I believe, is that the several fprintfs server-side "slow it down" and the client can keep the pace of the transmission. Note: this only happens for very large files. I did some experiments and the client seems to crash at about 15 MB, but I can't be certain of that. I can assure you that the client can download anything under 1 MB at super speed, the problem arises when the file is too big. Is there any way to solve this? I know it's hard to tell without the code in front of your eyes, but perhaps some of you have experienced the same issue

I guys. I have a Client - Server application. This simulates (via UDP socket) the Go-Back-N protocol, so you give a window dimension and it will simulate go back n. The code (both Client and Server) works and does what it is meant to do. The only problem lies in a segmentation fault client-side taking place when I remove fprintf server-side. Being the biggest challenge, I had to use several fprintf to debug the server. And, as long as those fprintf stay there it's all safe and sound, but the very moment I delete them, client will crash after having recieved some packets. I don't know why it happens, but I had more experienced people check my code and there are no bad accesses nor errors with pointers or malloc. So I don't really know what's happening. As I said, the code has got no formal error. What I believe, is that the several fprintfs server-side "slow it down" and the client can keep the pace of the transmission. Note: this only happens for very large files. I did some experiments and the client seems to crash at about 15 MB, but I can't be certain of that. I can assure you that the client can download anything under 1 MB at super speed, the problem arises when the file is too big. Is there any way to solve this? I know it's hard to tell without the code in front of your eyes, but perhaps some of you have experienced the same issue

Hi everyone. I'm trying to self study for C++ programming... Can anyone suggest me a few books that I should read based on your experience and give some advice to be consistent in programming?

https://t.me/cpp20programming

Based on the information you have provided, it is difficult to determine the exact cause of the segmentation fault without examining your code in detail. However, here are some general suggestions that you can try to solve this issue: Enable compiler warnings: Enable compiler warnings to check if there are any uninitialized variables or unused variables in your code. Fixing these issues might solve your problem. Check for memory leaks: Use a tool like Valgrind to check for memory leaks in your code. Memory leaks can cause segmentation faults and can be difficult to debug. Use a debugger: Use a debugger like gdb to debug your code. You can set breakpoints and step through your code to see where the problem is occurring. Optimize your code: If your code is running slowly, try to optimize it. Use profiling tools to identify the slow parts of your code and try to optimize them. Check for buffer overflow: If you are using buffers in your code, check if you are overflowing them. Buffer overflow can cause segmentation faults. Use defensive programming: Use defensive programming techniques like checking for null pointers and validating input to prevent unexpected behavior. Use logging instead of fprintf: Instead of using fprintf for debugging, use a logging library like Log4j or Log4cxx. This will help you to log the information you need without affecting the performance of your code. These are some general suggestions that you can try to solve your problem.

Segmentation fault is always about incorrect memory access. Have you tried to run your application under gdb or another debugger? You need to find a place in your code when your application crashes, otherwise there is almost no sense to talk about high level work of your app

Thank you very much! What are the tools to check if code is slow?

Based on the information you have provided, it is difficult to determine the exact cause of the segmentation fault without examining your code in detail. However, here are some general suggestions that you can try to solve this issue: Enable compiler warnings: Enable compiler warnings to check if there are any uninitialized variables or unused variables in your code. Fixing these issues might solve your problem. Check for memory leaks: Use a tool like Valgrind to check for memory leaks in your code. Memory leaks can cause segmentation faults and can be difficult to debug. Use a debugger: Use a debugger like gdb to debug your code. You can set breakpoints and step through your code to see where the problem is occurring. Optimize your code: If your code is running slowly, try to optimize it. Use profiling tools to identify the slow parts of your code and try to optimize them. Check for buffer overflow: If you are using buffers in your code, check if you are overflowing them. Buffer overflow can cause segmentation faults. Use defensive programming: Use defensive programming techniques like checking for null pointers and validating input to prevent unexpected behavior. Use logging instead of fprintf: Instead of using fprintf for debugging, use a logging library like Log4j or Log4cxx. This will help you to log the information you need without affecting the performance of your code. These are some general suggestions that you can try to solve your problem.

I guys. I have a Client - Server application. This simulates (via UDP socket) the Go-Back-N protocol, so you give a window dimension and it will simulate go back n. The code (both Client and Server) works and does what it is meant to do. The only problem lies in a segmentation fault client-side taking place when I remove fprintf server-side. Being the biggest challenge, I had to use several fprintf to debug the server. And, as long as those fprintf stay there it's all safe and sound, but the very moment I delete them, client will crash after having recieved some packets. I don't know why it happens, but I had more experienced people check my code and there are no bad accesses nor errors with pointers or malloc. So I don't really know what's happening. As I said, the code has got no formal error. What I believe, is that the several fprintfs server-side "slow it down" and the client can keep the pace of the transmission. Note: this only happens for very large files. I did some experiments and the client seems to crash at about 15 MB, but I can't be certain of that. I can assure you that the client can download anything under 1 MB at super speed, the problem arises when the file is too big. Is there any way to solve this? I know it's hard to tell without the code in front of your eyes, but perhaps some of you have experienced the same issue

It sounds like you have a complex issue with your Client-Server application. From what you’ve described, it seems that removing the fprintf statements on the server-side causes a segmentation fault on the client-side when transferring large files. It’s possible that the fprintf statements are slowing down the server enough for the client to keep up with the transmission. One way to approach this issue is to add some debugging statements on the client-side to see where exactly the segmentation fault is occurring. You could also try adding some delay or throttling on the server-side to see if that helps with the issue. Additionally, you could try using a different protocol such as TCP to see if that resolves the issue. Have you tried any of these approaches?

Bard? :)

Is there a way in the standard library (std=c++17) to create a date-time object and add a deltatime?

maybe https://en.cppreference.com/w/cpp/chrono/time_point

Yes, I saw that, but how could I specify a date with time?

there's example code, which demonstrates how to calculate the day before, so...?

Yes, but it starts with the current date, I want to specify a different date.

Yeah, but that's since C++20

I bet you've found this already, but nevertheless https://stackoverflow.com/a/70687148/5875417

Oh my god I take brain damage everytime someone decides to use UTC and ignore leap seconds and then proceeds to do anything milliseconds scale

Doesn't chrono account for leap milliseconds?

It doesn't need to before C++20

C++20 added partial support. Full support comes with C++23. In C++20, only leap second insertion was supported i.e. addition of leap seconds. C++23 supports both addition and subtraction.

It sounds like you have a complex issue with your Client-Server application. From what you’ve described, it seems that removing the fprintf statements on the server-side causes a segmentation fault on the client-side when transferring large files. It’s possible that the fprintf statements are slowing down the server enough for the client to keep up with the transmission. One way to approach this issue is to add some debugging statements on the client-side to see where exactly the segmentation fault is occurring. You could also try adding some delay or throttling on the server-side to see if that helps with the issue. Additionally, you could try using a different protocol such as TCP to see if that resolves the issue. Have you tried any of these approaches?

Hi, so the problem is that when many retransmission occur, a buffer client side is overwritten over the allowed dimension. That is, for some reason, unallowed memory chunks are overwritten, causing the segfault (confirmed by Valgrind). I can't change to TCP as this is a college project and I have to follow my professor's requests.

Does anyone know why the catch block doesn't handle exception it's just crash? Any ideas?

crash = segfault?

may it be in case if I trying to delete smth in catch block?

i want to learn C++ from scratch, are there any resources available here?