gzr | A Command Line Tool for Looker Content Management

I'm completing an assignment for the CS50x course, and I'm confident, after many tests, that the math within my code is correct. However, an embedded else-if statement is changing the values of the temp[height][width] array, which stores the hexadecimal values for the Blue, Green, and Red part of the pixel (i.e., temp[][].rgbtBlue, temp[][].rgbtGreen, temp[][].rgbtRed. For some reason, the value of this and it seems like no one else has had this frustrating bug.

To preface my code, the goal of the assignment is to filter an image in 4 different ways, and this final filter is edge detection. After initializing some arrays, I begin to go through each row (for loop with int i), then each pixel within that row (embedded for loop with int j), and height and width are the dimensions of the input image. Once within the embedded for loop, I put an if-else statement to check if the temp[i][j] pixel is a corner/edge, or neither, and I embedded further if-else-if statements within the if statement to determine if the temp[i][j] corner/edge pixel is a corner or an edge, which would slightly change how edges are detected.

The bug occurs in the else-if statement checking if the pixel is the lower left corner. For example, when temp[0][0].rgbtBlue is supposed to be 4, it becomes 7. Before this else-if loop, temp[0][0] is 4. It stays 7 for the rest of the parent if-else statement (the one meant to check for a corner/edge pixel, just under the embedded for (int j) loop). However, once this if-else statement ends, temp[0][0].rgbtBlue is 4, again, but the damage has already been done.

This bug is wild to me, especially because I'm fairly new to coding. I have absolutely no idea what to do. My best guess is that it has something to do with memory.