Thanks Stuart for your answer. I'm indeed running snapshots and after doing "pkg_delete xscreensaver; pkg_add gdb xscreensaver debug-xscreensaver" I was able to do the following: egdb /usr/local/libexec/xscreensaver/memscroller memscroller.core, which returns a lot information and has now for that reason increased my interest for memscroller.core.
Le dim. 9 août 2026 à 11:25, Stuart Henderson <[email protected]> a écrit : > On 2026-08-09, Andy <[email protected]> wrote: > > --00000000000022a1260658995a18 > > Content-Type: text/plain; charset="UTF-8" > > > > Hi misc! > > What is memscroller.core? After reading the manpage, it seems like > > something related to xscreensaver but I'm not quite sure. > > yes, > > $ pkglocate memscroller > > xscreensaver-6.15p1:x11/xscreensaver:/usr/local/libexec/xscreensaver/memscroller > <snip> > > it's a "coredump" (contents of the memory of the running process) from > when a run of that crashed. > > if you're on a release version of OpenBSD then you can probably get > more information (as long as the file is dated since you updated the > ls) - > > pkg_add gdb debug-xscreensaver > egdb /usr/local/libexec/xscreensaver/memscroller memscroller.core > bt full > > post the output (there will be a few screens full) in a post > to ports@ and maybe someone will be able to help track down the > cause. > > (if you're using snapshots then you're unlikely to still get a > debug-xscreensaver to match the installed build of xscreensaver, > but if you do "pkg_delete xscreensaver; pkg_add gdb xscreensaver > debug-xscreensaver" and delete the .core you'll be setup to > run the egdb command if it happens again). > > Do *not* post the core file itself, it may contain secrets. > > > > > > -- > Please keep replies on the mailing list. > >
