Subject: bug#30193: closed (Re: bug#30193: crash in libotf)

From: [email-masked] (GNU bug Tracking System)
Date: Fri, 02 Feb 2018 17:01:02 +0000

Your bug report

#30193: crash in libotf

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to [email-masked].

-- 
30193: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=30193
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: bug#30193: crash in libotf
From: Glenn Morris <[email-masked]>
To: [email-masked]
Date: Fri, 02 Feb 2018 11:47:08 -0500
List-Id: <debbugs-submit.debbugs.gnu.org>

To summarize:
This is an issue in the libotf library that Emacs uses.
It will be fixed in a future libotf release.
In the meantime, it can be worked around in Emacs by adding
"Noto Serif Kannada" to face-ignored-fonts.

Subject: The deadliest file in Emacs history
From: 積丹尼 Dan Jacobson <[email-masked]>
To: [email-masked]
Date: Sun, 21 Jan 2018 17:54:25 +0800
List-Id: <debbugs-submit.debbugs.gnu.org>

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