Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cmd/compile: empty ranges associated with inlined_subroutine entries in debug_ranges #23928

Closed
aarzilli opened this issue Feb 19, 2018 · 2 comments

Comments

Projects
None yet
3 participants
@aarzilli
Copy link
Contributor

commented Feb 19, 2018

What version of Go are you using (go version)?

1.10

What did you do?

compile anything, then objdump --dwarf exe | grep 'start == end'

What did you expect to see?

Nothing, ranges with start == end are superfluous.

What did you see instead?

Some.

cc @thanm

@aarzilli

This comment has been minimized.

Copy link
Contributor Author

commented Feb 19, 2018

Will send CL presently

@gopherbot

This comment has been minimized.

Copy link

commented Feb 19, 2018

Change https://golang.org/cl/94816 mentions this issue: cmd/compile: fix dwarf ranges of inlined subroutine entries

@ALTree ALTree added the Debugging label Feb 19, 2018

@ALTree ALTree changed the title cmd/compile: empty ranges associated with inlined_subroutine entries in debug_ranges [Debugging] cmd/compile: empty ranges associated with inlined_subroutine entries in debug_ranges Feb 19, 2018

@gopherbot gopherbot closed this in 87736fc Mar 1, 2018

@golang golang locked and limited conversation to collaborators Mar 1, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.