Regarding the alloca and malloc difference. You can't just change the code from alloca to malloc because malloc allocates memory from the heap and has to be free'd while alloca allocates memory from the stack and the memory is "free'd" when the function returns.
If you change the code from alloca to malloc you have to explicitly free the pointer returned by malloc. -- Vargas P.S.: Sorry by the duplicate mail Zooko, I've replied to you instead of replying to the group. On Tue, Sep 15, 2009 at 13:19, Zooko Wilcox-O'Hearn <[email protected]> wrote: > > Here is a patch that fixes that issue for me: > > http://allmydata.org/trac/pycryptopp/changeset?new=622% > 40cryptopp&old=620%40cryptopp > > This patch was initially committed to the pycryptopp repository in > two steps: > > http://allmydata.org/trac/pycryptopp/changeset/621/cryptopp > http://allmydata.org/trac/pycryptopp/changeset/622/cryptopp > > Regards, > > Zooko > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [email protected]. More information about Crypto++ and this group is available at http://www.cryptopp.com. -~----------~----~----~----~------~----~------~--~---
