Please review: C++ Translation

Python tests look okay to me, assuming they've been fixed in the last five years. Just commenting here to note that.

It was a good one!

That fits the 7 kyu of the kata.
If it were having more elaborate tests, this solution would timeout and the kata rank must then be 5 kyu or so.

SIGFPE fixed + RNG fixed

i rewrote the tester function

I raised an issue specific to incorrect setup of the random generator.

Still, tests in C do not crash for me and they work (more or less) as expected. I'd tend towards suggesting to look for the problem in your code, or posting it here so we could check it.

Please see this issue

C: srand should not be called in tester, otherwise it re-seeds RNG with every test case and causes repetitive inputs.

Seems like tests for C implementation crashing in random places with error 'Caught unexpected signal: SIGFPE (8). Erroneous arithmetic operation.'. I tried to catch problem n-values (thought it's my algorithm was incorrect), but seems like tests crashing before executing my realisation of divisors() directly.

In process I also discovered that generated n-values for tests repeating very often, in succession or periodicaly, so maybe random generator also broken for C implementation.

Hi. When asking for help, you need to be more specific: which language are you using? What is exactly your problem? What are you doing, and what is going wrong? Provide the exact logs that you are receiving.

You can post code, but if you do it don't forget to put on the spoiler flag on your message and to format your code correctly.

For more details and informations, you can refer to the official documentation: https://docs.codewars.com/training/troubleshooting/

my code takes less memory space than expected. so I'm supposed to add variables just to saturate?

Most probably the reason for your failure is *z not being set to a correct value, but still tests should not crash.

There's many possible reasons for SIGSEGV (https://docs.codewars.com/training/troubleshooting#c-c-signal-11---sigsegv), but it's difficult to tell what happens in your case without seeing the code.