[Libguestfs] libnbd golang failure on RISC-V
Daniel P. Berrangé
berrange at redhat.com
Thu Jun 9 18:30:59 UTC 2022
On Thu, Jun 09, 2022 at 05:33:03PM +0100, Richard W.M. Jones wrote:
> On Thu, Jun 09, 2022 at 07:22:45PM +0300, Nir Soffer wrote:
> > On Thu, Jun 9, 2022 at 6:48 PM Richard W.M. Jones <rjones at redhat.com> wrote:
> > > NB: this _does not_ address the other problem where GODEBUG=cgocheck=2
> > > complains about "fatal error: Go pointer stored into non-Go memory".
> >
> > Do we keep go pointers in buffers allocated in C?
>
> I guess we must do, but I'm not sure where.
>
> However it's possible that golang on RISC-V is buggy, particularly the
> somewhat old version that we are still using.
Yeah, my money is on this being a bug in the go runtime, the signal
stuff in particular is a bit hairy in the go impl that I looked at.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
More information about the Libguestfs
mailing list