Unmmatching valgrind error messages in tester about printftester HOT 6 CLOSED

After looking back at older commits, I managed to find a commit where the testers stopped working. All I did in that commit was change the library name. I started working from the commit before everything broke and all testers seem to run fine again. Will close this issue now, thanks for all the help :)

from printftester.

Hi, it's an invalid read here not a malloc error, you probably read too much in ft_parse_width, going back to an older version of the tester where there wasn't yet this test will obviously remove your problem. You can compile your project with -g3 to have the line number of the error.

from printftester.

Indeed, it cannot be a malloc issue, since I no longer use it there. The thing is that if I run a main with the above test (test 84 in %d tester) and check with valgrind, no invalid read shows up. Event ran vscode's debugger but no errors occurred. And also, I didn't use an older version of your tester, rather an older version of my code. Sorry about that.

from printftester.

Then you should check what you could have broken since your previous version, the test 84 is valid and should not be an issue. Sorry but I can't help you more than that good luck anyway.

from printftester.

I no longer know what is happening with the tester. For example, I get all these errors when running the tester on Linux (same KOs appear in mac). No matter what I change I still get those same KOs in the tester. I even commented the main loop that iterates over the string, and the tester still shows the very same OKs and KOs, even though all of them should be KO

from printftester.

I don't know what to say ... maybe on the side of your Makefile.
https://i.imgur.com/Q1O1Lvt.png

from printftester.