Added missing initialization

[rstephan]

As the headline says.

[Gadgetoid]

Perhaps @jgarff or @penfold42 can confirm if this is safe?

[penfold42]

It looks harmless.

But is it not pointless ? I thought the compiler guaranteed malloc gave zeros ?

[jgarff]

I think only calloc() is guaranteed to be zero'd. If it's the first allocation to the process from the kernel, it should be zero'd out for security reasons. If you free and malloc again though and it doesn't cause a kernel page fault for new memory, it's up to the c library, which I don't believe makes that guarantee, or at least it's not part of the C standard. I could be wrong, but that's what I remember at least.

…

On Fri, Mar 16, 2018 at 8:19 AM penfold42 ***@***.***> wrote: ***@***.**** commented on this pull request. It looks harmless. But is it not pointless ? I thought the compiler guaranteed malloc gave zeros ? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#219 (review)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIPem7IkfYsP1TgD8VUGm08qLqOBf5sTks5te8cKgaJpZM4PCiUs> .