Subject: bug#30193: The deadliest file in Emacs history

From: 積丹尼 Dan Jacobson <[email-masked]>
Date: Sun, 21 Jan 2018 17:54:25 +0800

Gentleman, I reveal to you the deadliest file in the history
of Emacs.

It is so deadly that it must be QP encoded, else, well,

Fatal error 11: Segmentation fault
Backtrace:
emacs[0x50a5fe]...
/lib/x86_64-linux-gnu/libpthread.so.0(+0x11fb0)[0x7fc827b75fb0]
/usr/lib/x86_64-linux-gnu/libotf.so.0(OTF_drive_gpos_with_log+0x2a)[0x7fc828527a2a]
/usr/lib/x86_64-linux-gnu/libm17n-flt.so.0(+0x24f2)[0x7fc8280e04f2]...

It is so deadly that once restored from QP, only emacs -nw can safely open it.

If you use X-windows, even doing "! cat"
(! runs the command dired-do-shell-command)
or just plain
$ emacs DEATH
will crash your emacs.
No matter if you do
# su - nobody
or even LC_ALL=C emacs ...
for the cleanest environment.

Oh yeah, here it is.

$ cat DEATH.qp
=E0=B2=B9=E0=B3=86=E0=B2=9A=E0=B3=8D=E0=B2=9A=E0=B3=81

It is so deadly that even in M-x shell,
just doing
$ qprint -d DEATH.qp
will fry your emacs.

emacs-version "25.2.2"
Debian emacs25 25.2+1-6