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

steven: go panics on run #73

Open
spotlightishere opened this issue Mar 12, 2016 · 4 comments
Open

steven: go panics on run #73

spotlightishere opened this issue Mar 12, 2016 · 4 comments

Comments

@spotlightishere
Copy link

I have an iMac running El Capitan (10.11.4). I installed go using Homebrew.

When I run steven, I'm getting this panic:

panic: reflect: reflect.Value.Set using value obtained using unexported field

goroutine 1 [running]:
panic(0x451af20, 0xc8202a2140)
    /usr/local/Cellar/go/1.6/libexec/src/runtime/panic.go:464 +0x3e6
reflect.flag.mustBeAssignable(0x1d9)
    /usr/local/Cellar/go/1.6/libexec/src/reflect/value.go:226 +0x161
reflect.Value.Set(0x46f3880, 0xc8200517a0, 0x1d9, 0x46f3880, 0xc820051650, 0x1d9)
    /usr/local/Cellar/go/1.6/libexec/src/reflect/value.go:1328 +0x25
github.com/thinkofdeath/steven.cloneBlock(0x56c7d40, 0xc820051650, 0x0, 0x0)
    /Users/joshua/Projects/Minecraft/go/build/src/github.com/thinkofdeath/steven/block.go:407 +0x282
github.com/thinkofdeath/steven.alloc(0x56c7d40, 0xc820051650, 0xc820051650)
    /Users/joshua/Projects/Minecraft/go/build/src/github.com/thinkofdeath/steven/block.go:389 +0x9ca
github.com/thinkofdeath/steven.init.5()
    /Users/joshua/Projects/Minecraft/go/build/src/github.com/thinkofdeath/steven/blocks.go:277 +0x6b2
github.com/thinkofdeath/steven.init()
    /Users/joshua/Projects/Minecraft/go/build/src/github.com/thinkofdeath/steven/world.go:23 +0x55ed
main.init()
    /Users/joshua/Projects/Minecraft/go/build/src/github.com/thinkofdeath/steven/cmd/steven/steven.go:    62 +0x4a

I do not have a steven-log.txt as it never generated/existed.

@0x277F
Copy link

0x277F commented Mar 12, 2016

@spotlightishere
Copy link
Author

I know it is not actively maintained anymore. I figured I would open this to see if anyone in the community knew how to fix it.

@Thinkofname
Copy link
Owner

I think either go 1.5 or 1.6 broke it due to me (unknowingly) relying on a bug.

@spotlightishere
Copy link
Author

Can confirm, downgrading to go 1.4 made it run as expected.

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

No branches or pull requests

3 participants