Skip to content

Always include debug symbols with -c dbg#3029

Merged
robfig merged 1 commit intobazel-contrib:masterfrom
fmeum:include-dbg-symbols-with-c-dbg
Dec 15, 2021
Merged

Always include debug symbols with -c dbg#3029
robfig merged 1 commit intobazel-contrib:masterfrom
fmeum:include-dbg-symbols-with-c-dbg

Conversation

@fmeum
Copy link
Copy Markdown
Member

@fmeum fmeum commented Dec 14, 2021

What type of PR is this?

Bug fix

What does this PR do? Why is it needed?

Previously, debugging a go_test target was only possible with an explicit --@io_bazel_rules_go//go/config:debug.

Which issues(s) does this PR fix?

Fixes bazelbuild/intellij#2313, which I think is more of a rules_go issue.

Previously, debugging a go_test target was only possible with an
explicit --@io_bazel_rules_go//go/config:debug.

Fixes bazelbuild/intellij#2313.
@robfig
Copy link
Copy Markdown
Contributor

robfig commented Dec 15, 2021

I'd normally be hesitant to add one-off rules for toggling existing flags or merge a change lacking tests, but this seems reasonable and low-risk and bazel-discuss seemed favorable towards it (https://groups.google.com/g/bazel-discuss/c/1_PC-Pj-nRg). Thanks

@robfig robfig merged commit 34a808c into bazel-contrib:master Dec 15, 2021
saser added a commit to saser/pdp that referenced this pull request Dec 26, 2021
This new version includes bazel-contrib/rules_go#3029 which has the effect that
building a benchmark with `-c dbg` and then running with
`-test.cpuprofile=<whatever>` lets `go tool pprof` see source information. This
is not the case with the most recently released version of rules_go, v0.29.0.

Also update Makefile so that `make buildifier` formats WORKSPACE.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Cannot debug go_test targets

2 participants