Morgan Aldridge <[email protected]> wrote: > Since Ian mentioned devel/zeal for a USE_NOBTCFI update in -current, I > figured I'd give it a try. Unfortunately, under OpenBSD > amd64/6.3-stable, I get the following error when attempting to execute > it: > > QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-username' > zeal.core.applicationsingleton: Singleton ID: > _nGQfwnfPpFrP7E8fa8MHCJw0S0KmYxfPsN0l86qrnY > zeal.core.applicationsingleton: Cannot attach to the shared memory > segment: "QSharedMemory::handle:: UNIX key file doesn't exist" > zeal.core.applicationsingleton: Cannot connect to the local service: > "QLocalSocket::connectToServer: Invalid name" > > There don't seem to be similar issues reported upstream. Can anyone > else confirm this issue or provide any insight before I report? > > I use an fvwm-based WM, not a full desktop environment, if there's > something for Qt apps that would need initialization in my .xsession > to initialize shared memory.
BIT/BTI failures result in SIGILL, generally visible in the shell. If you are not sure, you use ktrace -di + kdump, to see if there is a SIGILL. If there is no SIGILL, it is unrelated to USE_NOBTCFI.
