X segfaulted when I opened a window, Xorg.log.old only showed the
address without anything specific, no core dump was created and
xenodm automatically restarted.
After I logged in I checked ~/.xsession for possible indications, but
that file gets truncated on login.
I've restarted xenodm again, so the old Xorg.log.old containing the
generic "X segfaulted at addr 0x86..." is also gone.
Woul it make sense to save an old copy in analogy to Xorg.log.old
so crashes like this have a higher chance of being hunted down?
I haven't extensively tested this patch, but relogging into X now leaves
~/.xesssion-errors.old with logs from the previous session behind.
Index: app/xenodm//config/Xsession.in
===================================================================
RCS file: /cvs/xenocara/app/xenodm/config/Xsession.in,v
retrieving revision 1.2
diff -u -p -r1.2 Xsession.in
--- app/xenodm//config/Xsession.in 1 Jul 2022 20:42:06 -0000 1.2
+++ app/xenodm//config/Xsession.in 14 Nov 2022 16:47:03 -0000
@@ -7,6 +7,7 @@ exec_prefix="@exec_prefix@"
# redirect errors to a file in user's home directory if we can
errfile="$HOME/.xsession-errors"
+cp -f "$errfile" "$errfile.old" 2> /dev/null
if ( umask 077 && cp /dev/null "$errfile" 2> /dev/null )
then
exec > "$errfile" 2>&1
