mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-09-23 23:01:24 +02:00
78a7cb648c
When we dump a thread's state (show thread, panic) we don't know if anything is happening in Lua, which can be problematic especially when calling external functions. With this patch, the thread dump code can now detect if we're running in a global Lua task (hlua_process_task), or in a TCP or HTTP Lua service (task_run_applet and applet.fct == hlua_applet_tcp_fct or http_applet_http_fct), or a fetch/converter from an analyser (s->hlua != NULL). In such situations, it's able to append a formatted Lua backtrace of the Lua execution path with function names, file names and line numbers. Note that a shorter alternative could be to call "luaL_where(hlua->T,0)" which only prints the current location, but it's not necessarily sufficient for complex code.
The HAProxy documentation has been split into a number of different files for ease of use. Please refer to the following files depending on what you're looking for : - INSTALL for instructions on how to build and install HAProxy - BRANCHES to understand the project's life cycle and what version to use - LICENSE for the project's license - CONTRIBUTING for the process to follow to submit contributions The more detailed documentation is located into the doc/ directory : - doc/intro.txt for a quick introduction on HAProxy - doc/configuration.txt for the configuration's reference manual - doc/lua.txt for the Lua's reference manual - doc/SPOE.txt for how to use the SPOE engine - doc/network-namespaces.txt for how to use network namespaces under Linux - doc/management.txt for the management guide - doc/regression-testing.txt for how to use the regression testing suite - doc/peers.txt for the peers protocol reference - doc/coding-style.txt for how to adopt HAProxy's coding style - doc/internals for developer-specific documentation (not all up to date)