`bazel build` always stripping debugging symbols, regardless of invocation?

[chris...@gmail.com]

I'm trying to use gdb on a small golang binary, but I can't seem to prevent debugging symbols from being stripped away. I've tried:

# None of these work

$ bazel build -c dbg //:mytarget

$ bazel build -c dbg --strip=never //:mytarget

$ bazel build --strip=never //:mytarget

All produce a binary in a '<arch>_stripped' directory. All of them throw a warning in gdb about missing debugging symbols.

I'm using bazel v0.10.0 and rules_go v0.9.0. I can't seem to generate a debuggable binary with any flag combination I'd expect, and https://github.com/bazelbuild/rules_go/blob/master/go/modes.rst doesn't show an example so I'm unsure where I've misstepped.

[Nathan Chan]

Hi Christi,

There’s a bug in the current implementation that does not account for —strip == ‘never’. I found it yesterday while debugging for another colleague and have a fix. Will send a pr later today. 

Nathan

--
You received this message because you are subscribed to the Google Groups "bazel-go-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bazel-go-discu...@googlegroups.com.
To post to this group, send email to bazel-go...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bazel-go-discuss/b46cc818-5ec7-481b-ab86-7c35698998ed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[chris...@gmail.com]

Great, thanks! Mind forwarding along the PR number? I'd like to follow along so I can use that hash when it's merged.

[Nathan Chan]

It was merged yesterday to master. PR #1326

To view this discussion on the web visit https://groups.google.com/d/msgid/bazel-go-discuss/ea49069e-da50-45dc-b012-674802942ae8%40googlegroups.com.