Date: Wed, 21 Jun 2017 23:18:53 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 220184] clang 4.0.0 segfaults on buildworld Message-ID: <bug-220184-8-vvaMNTMTQY@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-220184-8@https.bugs.freebsd.org/bugzilla/> References: <bug-220184-8@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 Mark Millard <markmi@dsl-only.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |markmi@dsl-only.net --- Comment #3 from Mark Millard <markmi@dsl-only.net> --- (In reply to Chris Collins from comment #0) If you know adding some notes about the following sorts of points it might help with folks that look into this: A) Are all the failures for compiling DataFormatters/TypeSummary.cpp ? B) Does DataFormatters/TypeSummary.cpp sometimes compile okay (no Segmentation Fault)? If the answer to (A) is "no" then questions similar to (B) apply for the other failure points. I'll note that I had a context that was analogous to (A): no with (B): yes and it turned out that I had access to a system that had its memory settings poorly "optimized" (to the point of occasional unreliability). Clang 4 seemed to show this notably more than 3.9 did but it was not clang's problem. Of course I've no clue if such might apply to your context. But it illustrates that such additional notes can be helpful. --=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-8-vvaMNTMTQY>