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

Does not build: wrong argument in memcall.Protect: memcall.NoAccess... are functions #116

Closed
pzeinlinger opened this issue Aug 11, 2019 · 0 comments · Fixed by #117
Closed
Labels

Comments

@pzeinlinger
Copy link
Contributor

Describe the bug
A fresh go get of memguard results in vet errors.

github.com/awnumar/memguard/core

src/github.com/awnumar/memguard/core/buffer.go:84:29: cannot use memcall.NoAccess (type func() memcall.MemoryProtectionFlag) as type memcall.MemoryProtectionFlag in argument to memcall.Protect
src/github.com/awnumar/memguard/core/buffer.go:87:29: cannot use memcall.NoAccess (type func() memcall.MemoryProtectionFlag) as type memcall.MemoryProtectionFlag in argument to memcall.Protect
src/github.com/awnumar/memguard/core/buffer.go:121:30: cannot use memcall.ReadOnly (type func() memcall.MemoryProtectionFlag) as type memcall.MemoryProtectionFlag in argument to memcall.Protect
src/github.com/awnumar/memguard/core/buffer.go:142:30: cannot use memcall.ReadWrite (type func() memcall.MemoryProtectionFlag) as type memcall.MemoryProtectionFlag in argument to memcall.Protect
src/github.com/awnumar/memguard/core/buffer.go:165:29: cannot use memcall.ReadWrite (type func() memcall.MemoryProtectionFlag) as type memcall.MemoryProtectionFlag in argument to memcall.Protect
src/github.com/awnumar/memguard/core/exit.go:67:21: cannot use memcall.ReadWrite (type func() memcall.MemoryProtectionFlag) as type memcall.MemoryProtectionFlag in argument to memcall.Protect

To Reproduce
Steps to reproduce the behaviour:
go get github.com/awnumar/memguard

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant