Date: Mon, 22 Apr 2019 05:22:48 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 237459] devel/lutok is partially broken on i386; causes failures (segfaults) with kyua tests Message-ID: <bug-237459-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237459 Bug ID: 237459 Summary: devel/lutok is partially broken on i386; causes failures (segfaults) with kyua tests Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: jmmv@FreeBSD.org Reporter: ngie@FreeBSD.org Flags: maintainer-feedback?(jmmv@FreeBSD.org) Assignee: jmmv@FreeBSD.org The kyua tests currently fail on ^/stable/11 with i386 with SIGSEGV, like s= hown below. From https://ci.freebsd.org/job/FreeBSD-stable-11-i386-test/lastCompletedBuild/t= estReport/local.kyua.engine/kyuafile_test/kyuafile__load__missing_test_prog= ram/ : 20190422-034812 D 56392 utils/env.cpp:114: Environment variable 'TMPDIR' is '/tmp/kyua.FvyhWW/3961/work' Process with PID 56392 exited with signal 11 and dumped core; attempting to gather stack trace (no debugging symbols found)...Core was generated by `/usr/tests/local/kyua/engine/kyuafile_test -vunprivileged-user=3Dtests -r/tmp/kyua'. Program terminated with signal 11, Segmentation fault. (no debugging symbols found)...#0 0x2812a7f9 in lua_close () from /usr/local/lib/liblua-5.2.so #0 0x2812a7f9 in lua_close () from /usr/local/lib/liblua-5.2.so #1 0x2817404b in lutok::state::raw_state () from /usr/local/lib/liblutok.s= o.3 #2 0x2881c2c8 in ?? () #3 0xbfbfde58 in ?? () #4 0x2881c2c8 in ?? () #5 0x28818cb0 in ?? () #6 0x00000002 in ?? () #7 0x2810ae7c in list_global () from /libexec/ld-elf.so.1 #8 0x2885a000 in ?? () #9 0x080efc28 in typeinfo for std::__1::basic_ostream<char, std::__1::char_traits<char> > () #10 0x283c870c in .got () from /usr/lib/libc++.so.1 #11 0xbfbfde88 in ?? () #12 0x9aef3637 in ?? () #13 0x00000010 in ?? () #14 0x28818cb0 in ?? () #15 0x00000000 in ?? () GDB exited successfully Files left in work directory after failure: config, kyua.LSY5EX, kyuafile_test.core, one It seems that the issue with the tests is related to devel/lutok, not devel= /atf or devel/kyua, based on the stack trace. Given that hunch, I reproduced the issue on i386 with ^/stable/11 (so it's = not a Jenkins issue). I then cloned lutok from master (https://github.com/jmmv/lutok), rebuilt it, and am no longer able to repro= duce the issue. The one commit that stands out that might have fixed the issue (because the rest of the changes were autotools/Travis CI related) is https://github.com/jmmv/lutok/commit/a23c7b894cf50dea5e927e36a3578b720fffcf= 23 . --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-237459-7788>