So, would it be possible to have this segfault fixed in time for the release?
It is a very important fix at least for those running big endian machines (which includes powerpc and sparc). A different version of the fix (but equally good) is already commited in upstream's repository for some time, and also verified.
If you want the least disruptive change, one that can be applied in a wide range of releases, then the patch that I attached to this bug should be the first choice.
Anyway, a reply is welcome, even if only to say "no, it won't be accepted", so that I don't waste my time anymore. The technical background of *why* the bug happens and how to fix it is at
So, would it be possible to have this segfault fixed in time for the release?
It is a very important fix at least for those running big endian machines (which includes powerpc and sparc). A different version of the fix (but equally good) is already commited in upstream's repository for some time, and also verified.
http:// cgit.freedeskto p.org/libspectr e/commit/ ?id=35aa9dfac26 31de24a40d95d14 69acb52f379249
If you want the least disruptive change, one that can be applied in a wide range of releases, then the patch that I attached to this bug should be the first choice.
Anyway, a reply is welcome, even if only to say "no, it won't be accepted", so that I don't waste my time anymore. The technical background of *why* the bug happens and how to fix it is at
https:/ /bugs.edge. launchpad. net/ubuntu/ +source/ libspectre/ +bug/298139/ comments/ 5
Thanks, Rogério Brito.