From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 6D984138334 for ; Thu, 12 Sep 2019 20:39:22 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DC255E0A7F; Thu, 12 Sep 2019 20:39:16 +0000 (UTC) Received: from mail-io1-xd44.google.com (mail-io1-xd44.google.com [IPv6:2607:f8b0:4864:20::d44]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id ED016E09BE for ; Thu, 12 Sep 2019 20:39:15 +0000 (UTC) Received: by mail-io1-xd44.google.com with SMTP id b136so58104417iof.3 for ; Thu, 12 Sep 2019 13:39:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gentoo-org.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=0OcQsUQumK2HxpyYXKrUL7Xj73EGWlcx/zLLfhrNtyI=; b=fEG6Bfxd0qMmkmvsiKSfJXAJnc/Aq/aXkCwpa4ZpiVVKgM9wkQOTYaqthy8936MhHI gv6V9cfEvcF6n1Gkf92MD+gRni7CTwUyZtphBaLQXUivIvFrFZHQ1Gz1cy0Qg8pONh6m nwg0fHxNQwhZfxJ1kI0yPzLrsawu3uI68CleOSMZ5X8uy/h2oef4qBGcepx3/CJQmkc7 +p8JVDe8hqUc+a/7VDAk7AUj+3T+DYUe2JoYZFUtFslZAGi1/ewnF7aofKDOvYNwuGjC azNV4+VhC7DVoY9H0graiXvoDVb+N6HBjYH79yoqZaFQNNmw+FuHgjZFuL49wtikJrOS u2Rg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=0OcQsUQumK2HxpyYXKrUL7Xj73EGWlcx/zLLfhrNtyI=; b=G6Ey3xKedZ90kcYit5ezNz6Em/cMt7Z2F47F10LmhcMPPmmbAXLSd5aNYy6VwtOJXl t5FUXlX9jqHv1C5ddtgBXn5QGKSPuY3iI2rmR0f0GRhdZFiqJEiTLRIea+cG2vDQiYli IUIpCQmIOiqf+7nhNlwwsiygNvLrwQv8Rclx/QBn3LrD1nVPBcr+k3/P/jwlzH9ET/GA VojwULYYtnJqNbuSUYKCXQBgz+YUyuuWSNjweeMxCezYW40GzedqUMPLwqXC7urI/Lg9 J7jeVLCgRrG690dDW9jr/3zfDp5r2QLzLuTX41qKkQGAX1YFiMKxxHUwoVSVF+HNIOGJ vUnQ== X-Gm-Message-State: APjAAAUaQn8IMUD7GpqfHwcj6OwCscRfMZeHMrl7iCd6akH6NU0CwueX 2kKFP6B0XW2JelDKRgMSfDNwiLFWXtfRIl0o8ZeHNAFb X-Google-Smtp-Source: APXvYqyU9qk9y4EiDKL/QFY+7qBxzcX62p2cQKMVFxQui+uGeH6hVqyCjWe3VapF38zL+7bZFI6c2y1rD58DwyErwJs= X-Received: by 2002:a6b:b445:: with SMTP id d66mr7142661iof.269.1568320754484; Thu, 12 Sep 2019 13:39:14 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 References: <20190911172128.18885-1-williamh@gentoo.org> <20190911172128.18885-2-williamh@gentoo.org> <20190912000525.GB21591@whubbs1.dev.av1.gaikai.org> <20190913082028.7b478cb1@katipo2.lan> In-Reply-To: <20190913082028.7b478cb1@katipo2.lan> From: Alec Warner Date: Thu, 12 Sep 2019 13:38:53 -0700 Message-ID: Subject: Re: [gentoo-dev] [PATCH 1/3] go-module.eclass: introduce new eclass to handle go modules To: Gentoo Dev Content-Type: multipart/alternative; boundary="000000000000771de60592612172" X-Archives-Salt: 7bcb282c-27c0-4fdf-af27-aef0ae80192f X-Archives-Hash: 7a8ebfd8ca19e19412a507af3235c317 --000000000000771de60592612172 Content-Type: text/plain; charset="UTF-8" On Thu, Sep 12, 2019 at 1:20 PM Kent Fredric wrote: > On Wed, 11 Sep 2019 17:28:22 -0700 > Alec Warner wrote: > > > I don't care if you strip or not (I'm not even sure portage knows how to > do > > it for go binaries) but I'm fairly sure the reason isn't because > "upstream > > does not support stripping go binaries" because they clearly do...unless > > upstream is portage here...? > > I know rust at least has some sort of magic in place where if you do > strip a binary, the ability for it to produce useful stack traces when > it crashes is reduced. > ( In that, it can make use of debugging symbols without the aid of a > debugger ) > > I can imagine that could be a reason to not support it. > You definitely should not call 'strip' on a go binary. If you build with the aforementioned linker flags you still get proper panic backtraces, but also smaller binaries that you cannot load into gdb. Why 'strip' can't do this but the go compiler can seems to be a bug ;) -A --000000000000771de60592612172 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Thu, Sep 12, 2019 at 1:20 PM Kent = Fredric <kentnl@gentoo.org> = wrote:
On Wed, 1= 1 Sep 2019 17:28:22 -0700
Alec Warner <ant= arus@gentoo.org> wrote:

> I don't care if you strip or not (I'm not even sure portage kn= ows how to do
> it for go binaries) but I'm fairly sure the reason isn't becau= se "upstream
> does not support stripping go binaries" because they clearly do..= .unless
> upstream is portage here...?

I know rust at least has some sort of magic in place where if you do
strip a binary, the ability for it to produce useful stack traces when
it crashes is reduced.=C2=A0

( In that, it can make use of debugging symbols without the aid of a
debugger )

I can imagine that could be a reason to not support it.

You definitely should not call 'strip' on a go bin= ary. If you build with the aforementioned linker flags you still get proper= panic backtraces, but also smaller binaries that you cannot load into gdb.= Why 'strip' can't do this but the go compiler can seems to be = a bug ;)

-A
=C2=A0
--000000000000771de60592612172--