-
Notifications
You must be signed in to change notification settings - Fork 112
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
SIGSEGV when throwing my own exception #238
Comments
The following change fixes the problem, but can we expect that inspect method always returns null terminated string?
We might have the same problem in other places.
|
Could you use %V syntax as ngx_str_t on ngx_log_error? |
I think "%*s" works too. See http://lxr.nginx.org/source/src/core/ngx_string.c#0091 Anyway, I'll take care of it, but not right now. |
yyamano
added a commit
to yyamano/ngx_mruby
that referenced
this issue
Dec 5, 2016
matsumotory
added a commit
that referenced
this issue
Dec 5, 2016
Use RSTRING_LEN() instead of as.heap.ptr to fix SIGSEGV. Fixed #238
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I got SIGSEGV with the following config:
This is gdb output.
The text was updated successfully, but these errors were encountered: