Yichun Zhang
Yichun Zhang
@patthiel Yeah, that `error_log_file` directive is not very useful for general use. It was just a quick hack to allow emitting error logs to special devices like `/dev/stderr`, IIRC.
@thibaultcha Will you have a look at this. If it looks good to you, then feel free to merge this :) Thanks!
One concern is the 1 offset in the line numbers for the subsequent lines. This may break existing tests.
@thibaultcha Some tests may reference nginx.conf line numbers printed in the error log messages, like this: ``` runtime error: access_by_lua(nginx.conf:37):2: bad bad bad ```
@thibaultcha Actually some tests really want to check the nginx.conf line numbers. That's part of the things we want to check accurately.
@philipp-classen This breaks compatibility with earlier OpenResty versions. We'll need to be smarter here.
We're actually retiring this repo (as well as the openresty-systemtap-toolkit repo and others) in favor of the upcoming OpenResty Trace platform (with will have free access for OpenResty open source...
@soulbird You can try [OpenResty XRay](https://openresty.com/en/xray/) which supports both GC64 and non-GC64 modes of LuaJIT. It provides a free trial.
@yingshang It may just be that you indeed have very few or no JITted Lua code. All or most of your Lua code paths are interpreted. You can verify this...
@yingshang Then it seems that you are still using LuaJIT 2.0? LuaJIT 2.1 is much better.