Your message dated Thu, 21 Sep 2017 18:50:26 +0200 with message-id <1c5598ec-4693-ad52-0a33-cfe9034ec...@debian.org> and subject line Re: luajit: laujit segfaults on arm64 has caused the Debian Bug report #818616, regarding luajit: laujit segfaults on arm64 to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 818616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818616 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: luajit Version: 2.1.0~beta2+dfsg-1 Severity: important Dear Maintainer, Yay - luajit with arm64 support uploaded! However, whilst it builds, it doesn't appear to work at all. Running it gives an immediate segfault I installed the debug version (thank you debian for automatic dbgsym builds!) and got: $ luajit GNU gdb (Debian 7.10-1+b1) 7.10 ... Reading symbols from luajit...Reading symbols from /usr/lib/debug/.build-id/e0/82e0a7597824d1de104daad7beb534c4280041.debug...done. done. (gdb) directory src (gdb) run Starting program: /usr/bin/luajit Program received signal SIGSEGV, Segmentation fault. getcurrenv (L=0xffffb7d80378, L=0xffffb7d80378) at lj_api.c:76 76 return fn->c.gct == ~LJ_TFUNC ? tabref(fn->c.env) : tabref(L->env); (gdb) info stack #0 getcurrenv (L=0xffffb7d80378, L=0xffffb7d80378) at lj_api.c:76 #1 cpcall (L=0xffffb7d80378, func=0x404c08 <pmain>, ud=0x0) at lj_api.c:1062 #2 0x00000000004379d8 in lj_vm_cpcall () at buildvm_arm64.dasc:1182 #3 0x000000000042bc3c in lua_cpcall (L=L@entry=0xffffb7d80378, func=func@entry=0x404c08 <pmain>, ud=ud@entry=0x0) at lj_api.c:1079 #4 0x000000000040406c in main (argc=1, argv=0xfffffffff518) at luajit.c:564 I will investigate this further, but filing this bug for now in case it's obvious to anyone else what's up. ---- Kernel: Linux 3.18.0-rc3 (SMP w/6 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: unable to detect Versions of packages luajit depends on: ii libc6 2.22-3 ii libgcc1 1:5.3.1-8 ii libluajit-5.1-2 2.1.0~beta2+dfsg-1 ii libluajit-5.1-common 2.1.0~beta2+dfsg-1 luajit recommends no packages. luajit suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---On Thu, 21 Sep 2017 15:15:24 +0100 Edmund Grimley Evans <edmund.grimley.ev...@gmail.com> wrote: > I think this bug was fixed in 2.1.0~beta3. Can it be closed please? > Any objections? None, closing G. > > # tail -n 1 /proc/self/maps > ffffeb710000-ffffeb731000 rw-p 00000000 00:00 0 > [stack] > > # dpkg -i libluajit-5.1-2_2.1.0~beta2+dfsg-1_arm64.deb > libluajit-5.1-common_2.1.0~beta2+dfsg-1_arm64.deb > luajit_2.1.0~beta2+dfsg-1_arm64.deb > ... > # luajit -e 'print("x");' > Segmentation fault (core dumped) > > # dpkg -i libluajit-5.1-2_2.1.0~beta2+dfsg-3_arm64.deb > libluajit-5.1-common_2.1.0~beta2+dfsg-3_arm64.deb > luajit_2.1.0~beta2+dfsg-3_arm64.deb > ... > # luajit -e 'print("x");' > Segmentation fault (core dumped) > > # dpkg -i libluajit-5.1-2_2.1.0~beta3+dfsg-1_arm64.deb > libluajit-5.1-common_2.1.0~beta3+dfsg-1_all.deb > luajit_2.1.0~beta3+dfsg-1_arm64.deb > # luajit -e 'print("x");' > x > > # dpkg -i libluajit-5.1-2_2.1.0~beta3+dfsg-2_arm64.deb > libluajit-5.1-common_2.1.0~beta3+dfsg-2_all.deb > luajit_2.1.0~beta3+dfsg-2_arm64.deb > # luajit -e 'print("x");' > x > >
signature.asc
Description: OpenPGP digital signature
--- End Message ---
