code review 88030045: doc/debugging_with_gdb: use -w to strip debug info.

doc/debugging_with_gdb: use -w to strip debug info.
Don't advertise -s anymore.
Fixes issue 7793.

[minux1, 2014-04-16 04:20:18]

Hello golang-codereviews@googlegroups.com,

I'd like you to review this change to
https://code.google.com/p/go

[iant, 2014-04-16 05:07:15]

LGTM

I guess.  Actually I don't understand what that paragraph is doing there at all.
 I don't see why the doc about "debugging Go code with GDB" needs to mention
anything about how to omit debug information--after all, the effect will be to
make it impossible debug Go code with GDB.  The option is documented in the
linker docs, as it should be.  And if we need to mention this option here for
some reason, why would we mention it in the introduction?

[minux1, 2014-04-16 05:13:52]

On Wed, Apr 16, 2014 at 1:07 AM, <iant@golang.org> wrote:

> I guess.  Actually I don't understand what that paragraph is doing there
> at all.  I don't see why the doc about "debugging Go code with GDB"
> needs to mention anything about how to omit debug information--after
> all, the effect will be to make it impossible debug Go code with GDB.
> The option is documented in the linker docs, as it should be.  And if we
> need to mention this option here for some reason, why would we mention
> it in the introduction?
>
I think the reason it's mentioned there is that people might want to make
the binary smaller once done debugging it.

but -s is definitely for that job as it will make panic trances unreadable.

[minux1, 2014-04-16 05:19:29]

*** Submitted as https://code.google.com/p/go/source/detail?r=cecf5834e4ea ***

doc/debugging_with_gdb: use -w to strip debug info.
Don't advertise -s anymore.
Fixes issue 7793.

LGTM=iant
R=golang-codereviews, iant
CC=golang-codereviews
https://codereview.appspot.com/88030045

[gobot, 2014-04-16 05:28:51]

This CL appears to have broken the windows-amd64 builder.
See http://build.golang.org/log/7ef5d5b3c3dee12a1218a86f4cd1bf9ead647db7