Svante Signell, le jeu. 04 févr. 2021 10:30:57 +0100, a ecrit:
On Wed, 2021-02-03 at 18:52 +0100, Samuel Thibault wrote:
It seems that the go issues that we were meeting (segfaults etc.)
were due to the missing support for unwinding over signal
handling
with siginfo support. The fix is already committed upstream, I am uploading a fixed patch to debian-ports, and requeued the golang
packages that seemed affected.
Do you mean the patch:
glibc (2.31-10~0) unreleased; urgency=medium
* debian/patches/hurd-i386/unsubmitted-tiocflush.diff: Cope with
BSD 4.1-ish ioctl(..., TIOCFLUSH, NULL).
No, I mean where unwinding actually happens, in libgcc-s1,
* patches/unwind_siginfo: libgcc unwinding over signal trampolines
with SIGINFO.
On Wed, 2021-02-03 at 18:52 +0100, Samuel Thibault wrote:
It seems that the go issues that we were meeting (segfaults etc.)
were due to the missing support for unwinding over signal handling
with siginfo support. The fix is already committed upstream, I am
uploading a fixed patch to debian-ports, and requeued the golang
packages that seemed affected.
Do you mean the patch:
glibc (2.31-10~0) unreleased; urgency=medium
* debian/patches/hurd-i386/unsubmitted-tiocflush.diff: Cope with
BSD 4.1-ish ioctl(..., TIOCFLUSH, NULL).
On Thu, 2021-02-04 at 10:35 +0100, Samuel Thibault wrote:
Svante Signell, le jeu. 04 févr. 2021 10:30:57 +0100, a ecrit:
On Wed, 2021-02-03 at 18:52 +0100, Samuel Thibault wrote:
It seems that the go issues that we were meeting (segfaults etc.)
were due to the missing support for unwinding over signal
handling
with siginfo support. The fix is already committed upstream, I am uploading a fixed patch to debian-ports, and requeued the golang packages that seemed affected.
Do you mean the patch:
glibc (2.31-10~0) unreleased; urgency=medium
* debian/patches/hurd-i386/unsubmitted-tiocflush.diff: Cope with
BSD 4.1-ish ioctl(..., TIOCFLUSH, NULL).
No, I mean where unwinding actually happens, in libgcc-s1,
* patches/unwind_siginfo: libgcc unwinding over signal trampolines
with SIGINFO.
I just found out about the patched gcc-10 package. Then this patch has
to be applied also for gcc-11 and gcc-snapshot, right?
Which versions from upstream in Debian already have the patch applied?
Svante Signell, le jeu. 04 févr. 2021 10:39:32 +0100, a ecrit:
I just found out about the patched gcc-10 package. Then this patch
has to be applied also for gcc-11 and gcc-snapshot, right?
As I said, it was already commited upstream.
Which versions from upstream in Debian already have the patch
applied?
None: Debian is getting frozen, I don't know if doko will upload new
fixes, but that's not a problem anyway, this is now available from debian-ports.
On Thu, 2021-02-04 at 10:44 +0100, Samuel Thibault wrote:
Svante Signell, le jeu. 04 févr. 2021 10:39:32 +0100, a ecrit:
I just found out about the patched gcc-10 package. Then this patch
has to be applied also for gcc-11 and gcc-snapshot, right?
As I said, it was already commited upstream.
Which versions from upstream in Debian already have the patch
applied?
None: Debian is getting frozen, I don't know if doko will upload new
fixes, but that's not a problem anyway, this is now available from debian-ports.
gcc-11 is in experimental, so the code freeze should not affect it, or?
And the latest gcc-snapshot in sid is 20210204-1. Does that version
have the patch applied?
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 286 |
Nodes: | 16 (3 / 13) |
Uptime: | 86:32:19 |
Calls: | 6,496 |
Calls today: | 7 |
Files: | 12,099 |
Messages: | 5,277,030 |