On Mon, Feb 13, 2023 at 12:09:35PM +0100, Rafael Sadowski wrote: > On Mon Feb 13, 2023 at 11:48:47AM +0100, Martin Ziemer wrote: > > After upgrade to snapshot #1041, vim--no_x11-perl-python3-ruby segfaults > > with > > this message: > > msyscall b27a163c000 a7000 error > > Segmentation fault (core dumped) > > > > dmesg shows this message: > > [vim]52497/378016 pc=b27a16ab907 inside b278b3f9000-b278b404fff: bogus > > syscall > > > > kern.version: > > kern.version=OpenBSD 7.2-current (GENERIC.MP) #1041: Sun Feb 12 > > 23:25:01 MST 2023 > > > > The snapshot before this update was from one week ago: > > OpenBSD 7.2-current (GENERIC.MP) #1021: Sun Feb 5 09:52:50 MST 2023 > > > > The vim-packages without the flavor perl do not segfault. > > > > Happened on two amd64 systems. Compiling from ports did not resolve > > the issue. > > > > Thank you very much for your report. It is a known problem. It is being > worked on.
"Problem" meaning: base and packages are out of sync. "Worked on" meaning: new packages are being rebuilt after a libc major bump. They will be available in the coming days. If you follow -current you need to pay attention to library bumps, especially major ones. libc, libcrypto/libss are particularly impactful. Only update over a (major) bump if you are sure that corresponding packages are available. If a bump happens wait a couple of days before updating. vim and various ports libraries are built against libc 96.5, libperl pulls in libc 97.0. Two libcs in the same address space can't end well. It's not enough to rebuild vim only. All its dependencies need to be rebuilt as well. That's difficult to do unless you have a dedicated clean build machine (no older libraries/headers around, no packages installed) or you are using proot(1).
