From owner-freebsd-amd64@freebsd.org Thu Feb 16 12:25:11 2017 Return-Path: Delivered-To: freebsd-amd64@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3E3AACE087E for ; Thu, 16 Feb 2017 12:25:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 24DD91EE3 for ; Thu, 16 Feb 2017 12:25:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v1GCPARk096260 for ; Thu, 16 Feb 2017 12:25:11 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-amd64@FreeBSD.org Subject: [Bug 217138] head (e.g.) -r313783 sh vs. jemalloc asserts: include/jemalloc/internal/tsd.h:687: Failed assertion: "tsd_booted" Date: Thu, 16 Feb 2017 12:25:11 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: markmi@dsl-only.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Feb 2017 12:25:11 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217138 --- Comment #1 from Mark Millard --- (In reply to Mark Millard from comment #0) It turns out that the sh failure during buildworld also gets to __je_tsd_get (but a different way) and then fails the same assertion for "tsd_booted": : /usr/src/contrib/jemalloc/include/jemalloc/internal/tsd.h:687: Failed assertion: "tsd_booted" A back trace is: (lldb) bt * thread #1: tid =3D 100194, 0x0000000040554e18 libc.so.7`_thr_kill + 8, na= me =3D 'sh', stop reason =3D signal SIGABRT * frame #0: 0x0000000040554e18 libc.so.7`_thr_kill + 8 frame #1: 0x0000000040554ddc libc.so.7`__raise(s=3D6) + 64 at raise.c:52 frame #2: 0x0000000040554d50 libc.so.7`abort + 84 at abort.c:65 frame #3: 0x0000000040528790 libc.so.7`__je_tsd_fetch [inlined] __je_tsd_get + 248 at tsd.h:687 frame #4: 0x000000004052876c libc.so.7`__je_tsd_fetch [inlined] __je_tsd_fetch_impl(init=3Dtrue) at tsd.h:692 frame #5: 0x000000004052876c libc.so.7`__je_tsd_fetch + 212 at tsd.h:717 frame #6: 0x0000000040550cc0 libc.so.7`__free(ptr=3D0x0000000040a17720)= + 64 at jemalloc_jemalloc.c:2011 frame #7: 0x0000000000411328 sh`ckfree(p=3D) + 32 at memalloc.c:88 frame #8: 0x0000000000407cd8 sh`clearcmdentry + 76 at exec.c:505 frame #9: 0x0000000000406bfc sh`evalcommand(cmd=3D, flags=3D, backcmd=3D) + 3476 at eval.c:1182 frame #10: 0x0000000000405570 sh`evaltree(n=3D0x0000000040a1cde8, flags=3D) + 212 at eval.c:290 frame #11: 0x000000000041105c sh`cmdloop(top=3D) + 252 at main.c:231 frame #12: 0x0000000000410ed0 sh`main(argc=3D, argv=3D) + 660 at main.c:178 frame #13: 0x0000000000402f30 sh`__start + 360 frame #14: 0x0000000040434658 ld-elf.so.1`.rtld_start + 24 at rtld_start.S:41 It appears that setvar was not used but clearcmdentry (indirectly) gets the same sort of problem when this happens: (lldb) up 9 frame #9: 0x0000000000406bfc sh`evalcommand(cmd=3D, flags=3D, backcmd=3D) + 3476 at eval.c:1182 1179 if (lastarg) 1180 setvar("_", lastarg, 0); 1181 if (do_clearcmdentry) -> 1182 clearcmdentry(); 1183 } --=20 You are receiving this mail because: You are on the CC list for the bug.=