| 1 |
On Wed, 11 Sep 2019 17:28:22 -0700 |
| 2 |
Alec Warner <antarus@g.o> wrote: |
| 3 |
|
| 4 |
> I don't care if you strip or not (I'm not even sure portage knows how to do |
| 5 |
> it for go binaries) but I'm fairly sure the reason isn't because "upstream |
| 6 |
> does not support stripping go binaries" because they clearly do...unless |
| 7 |
> upstream is portage here...? |
| 8 |
|
| 9 |
I know rust at least has some sort of magic in place where if you do |
| 10 |
strip a binary, the ability for it to produce useful stack traces when |
| 11 |
it crashes is reduced. |
| 12 |
|
| 13 |
( In that, it can make use of debugging symbols without the aid of a |
| 14 |
debugger ) |
| 15 |
|
| 16 |
I can imagine that could be a reason to not support it. |
Archives