Date: Tue, 29 Apr 2025 20:44:50 +0200 From: Dimitry Andric <dim@FreeBSD.org> To: Shawn Webb <shawn.webb@hardenedbsd.org> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: HEADS UP: libllvm, libclang, and liblldb converted into shared libraries Message-ID: <BCE98495-A396-4BB2-AFE0-F70BF24DBCA7@FreeBSD.org> In-Reply-To: <e53actwlpwgclycisp2gitexzsf6s65lgprbimzyeed7jjsj4y@hz64csjqt7z6> References: <B44B37E9-16C8-46B2-95CA-2A9072174FFF@FreeBSD.org> <qbula3o6nf2f5xkpb4vu6p7d25of6z3hvtqfhr2x2rfr3flesh@6fzyxd7qnl3a> <8173C7D9-F95A-4440-82DA-6CF160AAD6C2@FreeBSD.org> <e53actwlpwgclycisp2gitexzsf6s65lgprbimzyeed7jjsj4y@hz64csjqt7z6>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On 29 Apr 2025, at 19:43, Shawn Webb <shawn.webb@hardenedbsd.org> wrote: > > On Sun, Apr 27, 2025 at 07:42:44PM +0200, Dimitry Andric wrote: >> On 27 Apr 2025, at 17:04, Shawn Webb <shawn.webb@hardenedbsd.org> wrote: >>> >>> On Sat, Apr 26, 2025 at 06:06:54PM +0200, Dimitry Andric wrote: >> ... >>>> Please let me know if you encounter any problems resulting due to this >>>> change, as I intend to MFC it. For example, I tried covering all >>>> incremental build scenarios, but I may have missed some corner case. >>> >>> Hey Dimitry, >>> >>> I suspect this may be a problem specific to HardenedBSD, but it looks >>> like cc occasionally crashes. It hits an assert at >>> /usr/src/contrib/llvm-project/clang/lib/Driver/Driver.cpp:2702. >>> >>> I can reproduce this by running `env SHELL=/bin/sh make buildenv` at >>> the top of /usr/src. Though, it doesn't reproduce 100%, but perhaps >>> around 60%. >> >> It's asserting on this line: >> >> assert(!CCGenDiagnostics && "stdin produces no crash reproducer"); >> >> I think during make buildenv the make framework will run cc --version >> and ld --version to get at the compiler and linker version, but it could >> be that it's doing some weird combination that hasn't been thought of. >> Can you get the exact command line out of the debugger? > > For some reason, I'm failing to figure out how to view the program's > invocation using lldb or gdb. But, running `strings > /usr/obj/usr/src/amd64.amd64/cc.core`, I see this, which may or may > not be the arguments passed to cc: > > ==== BEGIN OUTPUT ==== > "-cc1" "-ferror-limit" "19" "-o" "-" "-disable-free" "-E" "-x" "c" "-" "-tune-cpu" "generic" "-target-cpu" "x86-64" "-triple" > "x86_64-unknown-freebsd15.0" "-resource-dir" "/usr/lib/clang/19" "-isystem" "/usr/lib/clang/19/include" "-internal-externc-i > system" "/usr/include" "-std=gnu17" "-fskip-odr-check-in-gmf" "-ftrivial-auto-var-init=zero" "-fgnuc-version=4.2.1" "-ffp-con > tract=on" "-fno-experimental-relative-c++-abi-vtables" "-fno-file-reproducible" "-O0" "-fdebug-compilation-dir=/usr/obj/usr/s > rc/amd64.amd64" "-fcoverage-compilation-dir=/usr/obj/usr/src/amd64.amd64" "-faddrsig" "-mrelocation-model" "static" "-debugge > r-tuning=gdb" "-funwind-tables=2" "-mconstructor-aliases" "-clear-ast-before-backend" "-main-file-name" "-" "-mframe-pointer= > all" "-fdiagnostics-hotness-threshold=0" "-fdiagnostics-misexpect-tolerance=0" "-D" "__GCC_HAVE_DWARF2_CFI_ASM=1" > ==== END OUTPUT ==== > > I hope that helps. Otherwise, can you provide me a hint as to how to > get lldb/gdb to show the arguments passed to cc? "settings show target.run-args", but I just checked buildenv, and it really only runs "cc --version" twice. If you do that in a loop, does it sometimes crash? -Dimitry [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.2 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCaBEeIgAKCRCwXqMKLiCW oxjWAKDCSOH4aEyLjGoiOu/kASoBzjmJpACfWyyRSdMIL5Hcm6rdmQBtD0BzyRE= =OuKF -----END PGP SIGNATURE-----home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BCE98495-A396-4BB2-AFE0-F70BF24DBCA7>