I see this issue: https://github.com/golang/go/issues/19431
In the mentioned PR, Russ add the code to parse /proc//maps to get the
executable filename, and then read it to parse the section to get the GNU
build id, rather than the go build id, see the function: func
elfBuildID(file string)
I see this issue: https://github.com/golang/go/issues/19431
In the mentioned PR, Russ add the code to parse /proc//maps to get the
executable filename, and the read it to parse the section to get the GNU
build id, rather than the go build id, see the function: func
elfBuildID(file string)
Why doesn't read it at all I need to discussion all tools
On Fri, 7 Mar 2025, 5:22 am Zhang Jie (Kn), wrote:
> From the output of `readelf -l ` , we can see `.note.go.buildid` and
> `.text` sections are both loaded.
>
> I want to know why `.note.go.buildid` is loaded, it seems go source code
> d
>From the output of `readelf -l ` , we can see `.note.go.buildid` and
`.text` sections are both loaded.
I want to know why `.note.go.buildid` is loaded, it seems go source code
doesn't read it at all.
I read the discussion here: https://github.com/golang/go/issues/68652.
Looks like gobuildid s
On Wed, Mar 5, 2025 at 10:34 PM Björn Försterling
wrote:
>
> when trying to "go get" inside the "golang/tools" module (golang.org/x/tools)
> I cannot download any Go files:
> .../golang/tools (master) $ GOMODCACHE="$(pwd)/.godeps" go get
> go: no package to get in current directory
Well, that is
Can u tell me how can I fix this issues
On Thu, 6 Mar 2025, 8:34 am Björn Försterling, <
bjoern.foersterl...@gmail.com> wrote:
> Hello,
>
> when trying to "go get" inside the "golang/tools" module (
> golang.org/x/tools) I cannot download any Go files:
> .../golang/tools (master) $ GOMODCACHE="$(
