The debugger doesn't show pointer values (like 0xf800000040)

[willfaught]

So it seems like you can't tell if two pointers point to the same thing.

Latest version of macOS High Sierra (10.13.6 (17G65)), VSCode (1.28.0), and vscode-go (0.6.91).

[eternal-flame-AD]

I usually watch uintptr(x) to obtain the pointer value. Probably a hack but I think that helps in your case:)

[ramya-rao-a]

@willfaught Can you provide a small sample code and elaborate on what you would expect vs what actually is being shown?

[vscodebot]

This issue has been closed automatically because it needs more information and has not had recent activity. Thank you for your contributions.

[willfaught]

@ramya-rao-a Sure:

func TestX(t *testing.T) {
	var i, j int
	var p = &i
	var q = &j
	t.Logf("%#v %#v", p, q)
}

When run, you see output like:

=== RUN   TestX
--- PASS: TestX (0.00s)
    foofile_test.go:9: (*int)(0xc000018150) (*int)(0xc000018158)
PASS
ok  	foopackage	0.010s

When debugging TestX, you see these local variables:

The pointer addresses for p and q aren't shown there, so you can't tell if they're equal and thus point to the same thing:

p: <*int>
q: <*int>

Instead, you should see something like:

p: 0xc000018150 <*int>
q: 0xc000018158 <*int>

There should also be a way to drill down into them to view the values they point to, like you can for the *testing.T in that same screen shot.

[ramya-rao-a]

Thanks for the details @willfaught

This should be do-able as long as delve passes a different type for pointers.

PRs are most welcome to fix this.
Code Pointers:

• Build and Debug extension
• Debug the debugger
• variablesRequest is the place where we extract the information from delve to show in the variables pane

[willfaught]

@ramya-rao-a Great, thank you!

[ramya-rao-a]

This feature is now available in the latest version of the Go extension (0.8.0)
Thanks @brycekahle!