Re: [notaryproject/notary] arm64 self-check failures: runtime: marked free object in span 0xffff5ec83ac0, elemsize=208 freeindex=3 (bad use of unsafe.Pointer or having race conditions? try -d=checkptr or -race) (Issue #1708)
- To: debian-go@lists.debian.org
- Subject: Re: [notaryproject/notary] arm64 self-check failures: runtime: marked free object in span 0xffff5ec83ac0, elemsize=208 freeindex=3 (bad use of unsafe.Pointer or having race conditions? try -d=checkptr or -race) (Issue #1708)
- From: Simon Josefsson <simon@josefsson.org>
- Date: Tue, 04 Mar 2025 13:14:06 +0100
- Message-id: <[🔎] 87frjtt2lt.fsf@josefsson.org>
- In-reply-to: <notaryproject/notary/issues/1708/2686429354@github.com> (Tianon Gravi's message of "Wed, 26 Feb 2025 15:23:02 -0800")
- References: <notaryproject/notary/issues/1708@github.com> <notaryproject/notary/issues/1708/2686429354@github.com>
Should we do another upload of Go 1.24 into Debian with this patch?
I'm hoping it would fix this FTBFS:
https://buildd.debian.org/status/fetch.php?pkg=notary&arch=arm64&ver=0.7.0%2Bgit20240416.9d2b3b3%2Bds1-3&stamp=1741045040&raw=0
/Simon
Tianon Gravi <notifications@github.com> writes:
> tianon left a comment (notaryproject/notary#1708)
>
> FWIW, this is fixed in upstream Go now, and [backported to the Go 1.24
> branch](https://github.com/golang/go/commit/949eae84df4d0294c19378f939012707e4e1bb24)
> (so the next Go 1.24 release should include the fix). Perhaps we can
> backport the fix in Debian a bit early to unblock Notary (but
> regardless this issue is probably fair to close). 🤔
Attachment:
signature.asc
Description: PGP signature
Reply to: