New answers tagged

1

"The code seemingly blurs images without error" indicates a problem. "Seemingly" correct output is not exactly correct. It tells me that the actual digital data output needs to be checked byte by byte. Checking the image to see if it seems wrong (not so much right) is a useful tool, but close isn't good enough. That's why it's ...


1

Per the error log, some pixels are 0. Your code does not meet all of the conditions you set at: if ((k >= 0) && (k < height - 1) && (j > 0) && (j < width - 2))// What I can see is that j won't be higher than 0, it only stays less or equal. //... And if ((l >= 0) && (l < width - 1) && ((i > 0) &...


1

If code generates a seg fault, something is definitely wrong, period! End of story! Common newbie error. The code is trying to do something with argv[1] before verifying that argc == 2, and by extension, before verifying that argv[1] exists. Simply put, if there's no key, then argc = 1. That means that argv[1] doesn't exist. So, when the code tries to use ...


Top 50 recent answers are included