-
Notifications
You must be signed in to change notification settings - Fork 13
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
Core dump from PyChapel when returning string #81
Comments
I tried going the other way around, just passing a string in to chpl and I get this error call.py
with response.chpl
producing
|
Well, I knew returning strings wouldn't be supported, but we should really just error when we don't understand the type instead of reaching that point :( |
Verified that the argument example also gives the same error for me. I tried removing the "in" intent and it ended up freezing my machine for 10-15 minutes before I forcibly rebooted. I intend to try again on a different box to see if I can get it to run to completion or kill it in a kinder manner. |
With the Modified response.chpl: export
proc flip_bit(msg: string) {
writeln(msg);
} |
This seems rather "dramatic"...
call.py
and response.chpl
Yields the rather impressive error:
This is probably the least work I've ever had to do to cause a core dump. Kinda proud of myself right now.
BTW: This was on the way to sending in a string to be manipulated and returned. So that will be my NEXT ticket if you have advice.
The text was updated successfully, but these errors were encountered: