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

$ go version
go version devel go1.18-6e50991d2a Sat Aug 21 18:23:58 2021 +0000 linux/amd64

Does this issue reproduce with the latest release?

YES. This issue reproduced with 1.17 and earlier.

What operating system and processor architecture are you using (go env)?

$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/root/.cache/go-build"
GOENV="/root/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/root/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/root/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/mnt/h/1.code/7.godev/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/mnt/h/1.code/7.godev/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="devel go1.18-6e50991d2a Sat Aug 21 18:23:58 2021 +0000"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/mnt/h/1.code/02.Project/godev/demo/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build280056047=/tmp/go-build -gno-record-gcc-switches"

What did you do?

1. create a new file named "proc.go" located in a package named with "XXXruntime" (such as: "fakeruntime/proc.go");
2. the "fakeruntime" package above imported in the project named "demo";

 ├── demo.go
 ├── env.sh
 ├── fakeruntime
 │   └── proc.go
 └── go.mod

3. go build the "demo";
4. execute "objdump -sj .debug_gdb_scripts demo" ;
5. repeat step 3,4 several times (do not forget execute "go clean" first,or use go build -a).

demo/demo.go:

package main

import (
	"demo/fakeruntime"
	"fmt"
)

func main() {
	s := fakeruntime.FakeRuntimeStruct{A: 1}
	fmt.Println(s)
}

demo/fakeruntime/proc.go

package fakeruntime

type FakeRuntimeStruct struct {
	A int
}

What did you expect to see?

When executed "objdump -sj .debug_gdb_scripts demo". the contents of section .debug_gdb_scripts should be "$GOROOT/src/runtime/runtime-gdb.py".
like this:

What did you see instead?

Sometimes, the contents of section .debug_gdb_scripts is as follows:

Reason

in the linking procedure:
the final value of the variable “gdbscript” will not be unique any more, if the project contains another file named like "XXXruntime/proc.go".
The whole process is executed by different go-routines as follows:
the variable “gdbscript” was assigned in the function "writeDirFileTables" which is executed by different goroutines in parallel .
if another file whose name ended with "runtime/proc.go" (not "$GOROOT/src/runtime/proc.go") was found firstly, the final value of the variable “gdbscript” will not be "$GOROOT/src/runtime/runtime-gdb.py".

the code is as follows: