Double free or corruption (!prev): 0x63f00550

[techninja1008]

I believe this relates to the following line:

pkcs11/pkcs11.go

Line 1332 in 6120d95

C.free(unsafe.Pointer(sig))

I encountered this whilst using ThalesIgnite/crypto11 to add PKCS#11 support to cloudflare/cfssl. This seems to only occur on ARM, as the trace comes from running it on a raspberry pi, and I have been able to get it to work successfully on x86.

Full trace can be found at https://pastebin.com/au1ieLbp

[techninja1008]

I have confirmed that this indeed only occurs on ARM.

[miekg]

[ Quoting <notifications@github.com> in "Re: [miekg/pkcs11] Double free or c..." ]

I have confirmed that this indeed only occurs on ARM.

That code doesn't look wrong to me. How can a double free be arch specific? C compiler?

[techninja1008]

I'm genuinely not sure, however I do know that it's the difference between compiling on Ubuntu 18.04 x86_64 and Raspbian stretch lite (with latest stable release of Go) on a Raspberry Pi 3 (armhf). I'll check later to see which C compiler is being used, but it's going to be from the distribution.

…

On Sun, Mar 17, 2019, 1:04 PM Miek Gieben ***@***.***> wrote: [ Quoting ***@***.***> in "Re: [miekg/pkcs11] Double free or c..." ] >I have confirmed that this indeed only occurs on ARM. That code doesn't look wrong to me. How can a double free be arch specific? C compiler? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#103 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEA4lbZlyXBGEFNWbFSlbD19hQGTOvs1ks5vXj1tgaJpZM4b4Qz2> .

[techninja1008]

Would GCC 6.3.0 on ARM vs GCC 7.3.0 on x86_64 do it?

[techninja1008]

Cross compiling to ARM on an x86_64 host using GCC 7.3.0 still yields the same result. Could it be a GO ARM bug?

[miekg]

[ Quoting <notifications@github.com> in "Re: [miekg/pkcs11] Double free or c..." ]

Cross compiling to ARM on an x86_64 host using GCC 7.3.0 still yields the same result. Could it be a GO ARM bug?

Maybe? Ive never debugged such a thing. Playing around with golang versions might yields some insights (and is relatively easy to do).

[dogusural]

Is there any update on the problem ? i am having a very similar issue on arm linux .

[miekg]

[ Quoting <notifications@github.com> in "Re: [miekg/pkcs11] Double free or c..." ]

Is there any update on the problem ? i am having a very similar issue on arm linux .

Is there an PR?