• go issues

    From Samuel Thibault@21:1/5 to All on Wed Feb 3 19:00:01 2021
    Hello,

    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.

    Samuel

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Svante Signell@21:1/5 to Samuel Thibault on Thu Feb 4 10:40:02 2021
    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?

    Thanks!

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Samuel Thibault@21:1/5 to All on Thu Feb 4 10:40:02 2021
    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.

    Samuel

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Samuel Thibault@21:1/5 to As I on Thu Feb 4 10:50:01 2021
    Svante Signell, le jeu. 04 févr. 2021 10:39:32 +0100, a ecrit:
    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?

    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.

    Samuel

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Svante Signell@21:1/5 to Samuel Thibault on Thu Feb 4 11:00:02 2021
    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?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Samuel Thibault@21:1/5 to All on Thu Feb 4 11:00:02 2021
    Svante Signell, le jeu. 04 févr. 2021 10:54:14 +0100, a ecrit:
    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?

    Yes, that one will get it on next upload.

    And the latest gcc-snapshot in sid is 20210204-1. Does that version
    have the patch applied?

    Most probably.

    Samuel

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)