Update the build configuration to always include debug symbols in LuaJIT bytecode objects

evo-lua / evo-luvi

[Obsolete] Experimental Lua runtime environment built on Luvi (libuv + LuaJIT)

https://evo-lua.github.io

Apache License 2.0

1 stars 0 forks source link

Closed rdw-software closed 1 year ago

rdw-software commented 1 year ago

Goals:

[x] When generating Lua bytecode objects, the-bg flag is used to enable readable stack traces for runtime code

This helps LuaJIT produce human-readable stack traces:

~~The only question is what the most convenient way to use this is.~~

~~Maybe~~ it's ~~even~~ worth always including those symbols in release builds ?

Split off from #4 since it's a trivial change that can already be implemented.

rdw-software commented 1 year ago

As for always including debug symbols:

This would (obviously) only be needed for Lua object files, not C code
It's going to waste some space, but how much exactly is difficult to predict
WITHOUT those symbols, the executable is currently 7.714 KB (statically-linked deps, WSL build)
WITH debug symbols, the size is 7.750 KB (same build settings otherwise)

Considering this is a huge QOL boost and averages to about 0.75KB per linked Lua file... I am inclined to just enable this by default.