We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
After upgrading to Go 1.6 i get a panic:
panic: runtime error: cgo argument has Go pointer to Go pointer
goroutine 5 [running]: panic(0x42157c0, 0xc8200e6050) /usr/local/go/src/runtime/panic.go:481 +0x3e6 code.google.com/p/portaudio-go/portaudio._cgoCheckPointer1(0x4194520, 0xc8200ec000, 0x0, 0x0, 0x0, 0x4184060) ??:0 +0x4d code.google.com/p/portaudio-go/portaudio.OpenStream(0x0, 0x0, 0x0, 0xc820016240, 0x1, 0xd9fb92, 0x40e5888000000000, 0x400, 0x0, 0xc8200e6000, ...) /Users/jpad/gocode/extern/src/code.google.com/p/portaudio-go/portaudio/portaudio.go:502 +0x3d1 ...
I think this caused by the stricter 1.6 rules about Go/C memory sharing? Is there a way around it?
The text was updated successfully, but these errors were encountered:
Ah, browsing the old issues i found out that this issue has been fixed already. All i needed to to was update my portaudio package, thanks!
Sorry, something went wrong.
No branches or pull requests
After upgrading to Go 1.6 i get a panic:
panic: runtime error: cgo argument has Go pointer to Go pointer
goroutine 5 [running]:
panic(0x42157c0, 0xc8200e6050)
/usr/local/go/src/runtime/panic.go:481 +0x3e6
code.google.com/p/portaudio-go/portaudio._cgoCheckPointer1(0x4194520, 0xc8200ec000, 0x0, 0x0, 0x0, 0x4184060)
??:0 +0x4d
code.google.com/p/portaudio-go/portaudio.OpenStream(0x0, 0x0, 0x0, 0xc820016240, 0x1, 0xd9fb92, 0x40e5888000000000, 0x400, 0x0, 0xc8200e6000, ...)
/Users/jpad/gocode/extern/src/code.google.com/p/portaudio-go/portaudio/portaudio.go:502 +0x3d1
...
I think this caused by the stricter 1.6 rules about Go/C memory sharing? Is there a way around it?
The text was updated successfully, but these errors were encountered: