On 2025-10-31 22:31:01 +0000, David wrote: > On Fri, 31 Oct 2025 at 22:04, Greg Wooledge <[email protected]> wrote: > > It doesn't crash for me (on Trixie). It causes xterm to write some > > information to the screen, and then 2 seconds go by, and then the > > xterm closes cleanly (because no shell was requested). > > Oh thanks, sorry, I misused the word "crash", it didn't crash, it just > closed the same as what you saw. > > I mistakenly assumed "crash" because of the context, and I didn't > understand why until you explained. Thanks for pointing that out.
Hmm... I forgot that this depends on another config. You also need to set reverseWrap (very useful in cooked mode). I've tested after removing my default config: $ xterm -k8 -xrm '*VT100.reverseWrap: true' -e 'printf "\x9a\x85\x08"; sleep 2' Segmentation fault (core dumped) $ echo $? 139 -- Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)
