Re: SIGSEGV in LuaJIT 2.1 VM
- From: Igor Ehrlich <igor.a.ehrlich@xxxxxxxxx>
- To: luajit@xxxxxxxxxxxxx
- Date: Fri, 18 Nov 2016 18:05:26 +0300
there is no virtualization at all, bare metal computers having mostly
Intel E5-2620
Well, shame on my prediction skills :)
For the sake of investigation, you say "mostly", so there are different
chips as well. Could you possibly list models where the issue occurs and
where it does not occur for you? If it's not a sensitive info, ofc.
Thanks in advance.
On Fri, Nov 18, 2016 at 5:56 PM, Peter Cawley <corsix@xxxxxxxxxx> wrote:
On Fri, Nov 18, 2016 at 2:52 PM, Tomas Kvasnicka <nzt4567@xxxxxxx> wrote:
- lvmst (part of openresty-gdb-utils) shows different trace number then
the one which contains the address in RIP
This isn't overly surprising - the faulting instruction is the one
which sets the current-trace variable, so until it executes, lvmst
will be reporting the old value of the variable.
Other related posts:
