On Sat, May 28, 2022 at 02:56:08PM +0200, Matthieu Herrb wrote: > On Sat, May 28, 2022 at 10:42:39AM +0100, Luis Henriques wrote: > > >Synopsis: Xorg segfauls shortly after upgrade to latest snapshot (27 May) > > >Category: system > > >Environment: > > System : OpenBSD 7.1 > > Details : OpenBSD 7.1-current (GENERIC.MP) #557: Fri May 27 > > 23:32:40 MDT 2022 > > > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > > > Architecture: OpenBSD.amd64 > > Machine : amd64 > > >Description: > > Shortly after upgrading to the latest snapshot, and running 'pkg_add > > -u', Xorg crashed. I'm attaching the Xorg.0.log file, which seems to > > point to a bug in ws. > > >How-To-Repeat: > > No idea how to repeat it. > > >Fix: > > Hi, > > If you think my recent commit to ws.c causes this, this commit only > removes a bogus call to free() in the error path of a failed memory > allocation. You're very unlikely to have reached that code branch in a > normal situation.
Maybe I shouldn't have mentioned ws at all; I just did because it is mentioned on the log but it's possible (likely?) that those "unknown command" errors are consequences of the crash and not the reason for it. > Without a way to reproduce the crash and without a stack trace, it's > going to be hard to tell where the bug is or to fix it. Yeah, I couldn't find any further information to help (no stack traces on the logs, or a core file). Sorry for not being very useful. Cheers, -- Luís
