panic: runtime error: invalid memory address or nil pointer dereference

[mohuishou]

run gopkgs in windoes 10
go version: go version go1.10.1 windows/amd64
It is not clear what caused the error.

gopkgs
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x0 addr=0x18 pc=0x57ea52]

goroutine 37 [running]:
github.com/MichaelTJones/walk.(*WalkState).visitFile(0xc0421101e0, 0xc0434d6780, 0x3b, 0x0, 0x0)
        E:/SoftFile/GOPATH/src/github.com/MichaelTJones/walk/walk.go:108 +0x2f2
github.com/MichaelTJones/walk.(*WalkState).visitChannel(0xc0421101e0)
        E:/SoftFile/GOPATH/src/github.com/MichaelTJones/walk/walk.go:71 +0xa2
created by github.com/MichaelTJones/walk.Walk
        E:/SoftFile/GOPATH/src/github.com/MichaelTJones/walk/walk.go:157 +0x1b9

[uudashr]

@mohuishou does the panic consistent on every gopkgs?

[mohuishou]

yes， every gopkgs panic

[mohuishou]

I found the cause of the error.There is a non-existent file in my gopath directory.
In this case，in MichaelTJones/walk/walk.go, file.info is nil
So that leads to this error.
The problem was solved after the file was deleted.

if err != nil && (!file.info.IsDir() || err != SkipDir) {
    ws.setTerminated(err)
    return
}

[uudashr]

What do you mean with non-existent file in gopath? What file?
How to reproduce the error? and how to fix it?

[wsw0108]

'NUL'

[mohuishou]

Sorry for the poor English.Have a file when deleting Windows will appear "file not found" error.

[uudashr]

So I'd better to close this. If these anything else related to this, then I'll reopen the issue.

[wsw0108]

@mohuishou Please check if there are files with name NUL, CON, etc, which has special meaning under Windows.

[uudashr]

Need help here.
@mohuishou can you update the and run the gopkgs command

$ go get -u github.com/uudashr/gopkgs/cmd/gopkgs
$ gopkgs -format '{{.Name}};{{.ImportPath}}'

I want to know if the error still exists

[no-response]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.