… that's not in the current function, we guess that LuaJIT forgot to tell us about a return and move up a stack frame. We do this even if the stack frame above doesn't work either. Now, we check if the stack frame above actualy works. If it doesn't, we complain, but we don't move up the extra stack frame.
…f the top of the trace stack, and then there's line info, we crash trying to find out about the line. To fix it, all we do is ignore line info if we've traced off the top of the stack.
…ms without causing others for Linux
typos + add missing word. Two fixes aren't quite right, but I don't know how to cherry-pick from here...
…thing if there's no recorder
…d copes if you call report without tracing (it writes an empty report)
…tall it to test it
…string was for, and needed -lrt
…e the executable bit will survive
…e finding two lua.h's. There must be an easier way