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

panic: "unexpected signal during runtime execution" #13

Closed
mappu opened this issue Mar 9, 2017 · 2 comments
Closed

panic: "unexpected signal during runtime execution" #13

mappu opened this issue Mar 9, 2017 · 2 comments

Comments

@mappu
Copy link

mappu commented Mar 9, 2017

Hi, thanks so much for releasing this binding.

I'm trying to track down a strange panic when this library is combined with some others. It's entirely possible that it has nothing to do with DataDog/zstd, but i can't reduce my test case any further.

Would you be able to comment on golang/go#19468 (comment) ?

Is there any chance the C code in this library is writing to memory it doesn't own?

@Viq111
Copy link
Collaborator

Viq111 commented Mar 14, 2017

Hi @mappu, I'm following the original issue at golang/go#19468 (comment) and not sure I can add more information.

You are using the Compress method in your example which is really simple and 20 lines of code (source) so I don't think there is something from the bindings side.

Looking at the C code, there is an object allocation "outside" the go code for the context (source), but this is created and freed during the C call so it shouldn't make the go runtime panic.

@mappu
Copy link
Author

mappu commented Jun 13, 2017

In the end, this issue was resolved by microsoft/go-winio#48 in the other repository. Closing!

@mappu mappu closed this as completed Jun 13, 2017
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

2 participants