-
Notifications
You must be signed in to change notification settings - Fork 202
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
segmentation fault in lj_vm_growstack_f #25
Comments
@tokers LuaJIT is not multi-thread safe in general. I know very little about your setup, maybe it's using multiple OS threads. Not sure. Your backtrace looks like a stack corruption or heap corruptions. Such things are not usually debuggable without a reproducible environment. |
There is only one OS thread in our service. We used the Mozilla rr recorded the crash environment, but only get a few clues.
The
BTW, here is the registers information when 0x411d2730 was changed:
|
By the way, someone replied this problem in the luajit maillist: https://www.freelists.org/post/luajit/segmentation-fault-in-lj-vm-growstack-f,1. |
@agentzh |
Hello!
We occurred a segmentation fault in LuaJIT. The backtrace is:
It seems that data inside
%rbp
was corrupted?We are using the asynchronous OpenSSL mode (with the dasync engine), it uses it's own co-routines. I don't know whether this can influence LuaJIT.
The segmentation fault disappeared after disabling the
SSL_MODE_ASYNC
. In addition, the frequency of this exception will reduce if disables JIT.Our LuaJIT version is https://github.com/openresty/luajit2/releases/tag/v2.1-20171103 .
The Linux Kernel version is 4.9.0.
I also opened an issue in here: openssl/openssl#6864 .
Is there any idea for the fixup or work-around? Thanks!
The text was updated successfully, but these errors were encountered: