Date: Thu, 22 Jun 2017 17:47:02 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-toolchain@FreeBSD.org Subject: [Bug 220184] clang 4.0.0 segfaults on buildworld Message-ID: <bug-220184-29464-u5fsAYbNae@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-220184-29464@https.bugs.freebsd.org/bugzilla/> References: <bug-220184-29464@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220184 --- Comment #8 from Dimitry Andric <dim@FreeBSD.org> --- I cannot reproduce this crash with the sample you provided. I tried: * clang 4.0.0 (297347) on FreeBSD 11.1-BETA1 i386 and amd64 * clang 4.0.0 (297347) on FreeBSD 12.0-CURRENT i386 and amd64 * clang 5.0.0 (305575) on FreeBSD 12.0-CURRENT i386 and amd64. It doesn't use a lot of memory either, roughly 250M max RSS: 8.37 real 8.19 user 0.16 sys 249616 maximum resident set size 48201 average shared memory size 268 average unshared data size 249 average unshared stack size 54447 page reclaims 6410 page faults 0 swaps 32 block input operations 5 block output operations 0 messages sent 0 messages received 0 signals received 20 voluntary context switches 459 involuntary context switches So memory starvation is pretty unlikely. I would suspect hardware issues, = in this case. --=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-220184-29464-u5fsAYbNae>