Date: Wed, 9 Oct 2024 10:06:03 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Paul Floyd <paulf2718@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: Problems with FreeBSD-15.0-CURRENT-amd64-20241003 Message-ID: <ZwYrWwd5XU_TRbEw@kib.kiev.ua> In-Reply-To: <7bdb3c71-8a36-444e-8b1d-9c4f789fe638@gmail.com> References: <7bdb3c71-8a36-444e-8b1d-9c4f789fe638@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Oct 09, 2024 at 06:35:08AM +0000, Paul Floyd wrote: > Hi > > I don't often update my 15-0-CURRENT VM. I did last week and I'm getting > several issues. > > Firstly, a bit annoying, both pkg and ksh93 fail to run, giving. > ld-elf.so.1: Shared object "libmd.so.6" not found, required by "ksh93" > > Next I'm getting a lot of new Valgrind test failures. I haven't done any > detailed debugging yet. > > One hang in a DRD test calling syscall 454 SYS__umtx_op. > > One for me, it looks like libc sendmsg has been re-implemented to use > socketcall. > > The biggest problem is with Helgrind. All apps now generate an extra error > > ==68593== Thread #1: Exiting thread still holds 1 lock > ==68593== at 0x4BBB5DA: _exit (in /lib/libsys.so.7) > ==68593== by 0x49FC1C0: exit (in /lib/libc.so.7) > ==68593== by 0x491CA10: __libc_start1 (in /lib/libc.so.7) > ==68593== by 0x20182F: (below main) (crt1_s.S:83) This is intended, see 3f3ec4b99f79d32a0bf15495559ca9883bd751f2. > > I tried building Helgrind with pthread tracing turned on but that just gave > me one more problem - a crash due to the tracing fprintf > (https://bugs.kde.org/show_bug.cgi?id=494327). > > A+ > Paul >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZwYrWwd5XU_TRbEw>