--===============0990481595== Content-Type: multipart/alternative; boundary="000000000000bc3e25058da53034" --000000000000bc3e25058da53034 Content-Type: text/plain; charset="UTF-8" On Fri, May 31, 2019 at 9:59 AM Matthias Clasen wrote: > I've spent some time tracking down a GTK+ / Pango crash ( > https://gitlab.gnome.org/GNOME/pango/issues/346 ). > > Turns out that there was a thinko in our original color glyph patch. We > can't modify the passed-in text. > > Here is a quick fix: > > > https://github.com/matthiasclasen/cairo/commit/79ad01724161502e8d9d2bd384ff1f0174e5df6e > > This probably needs to go into a stable cairo branch too. > Hi, two months on, this is still not in git. It is a very easy memory corruption patch. We ship the patch in Fedora, but I would prefer to not rely on distros to pick through the rubble. Can we get this merged, please ? --000000000000bc3e25058da53034 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Fri, May 31, 2019 at 9:59 AM= Matthias Clasen <matthias.= clasen@gmail.com> wrote:
I've spent s= ome time tracking down a GTK+ / Pango crash ( https://gitlab.gnome.org/G= NOME/pango/issues/346 ).

Turns out that there = was a thinko in our original color glyph patch. We
can't modi= fy the passed-in text.

Here is a quick fix:


This probably needs to go into a stable ca= iro branch too.

Hi, two mon= ths on, this is still not in git. It is a very easy memory corruption patch= .
We ship the patch in Fedora, but I would prefer to not rely on = distros to pick through
the rubble. Can we get this merged, pleas= e ?
--000000000000bc3e25058da53034-- --===============0990481595== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline LS0gCmNhaXJvIG1haWxpbmcgbGlzdApjYWlyb0BjYWlyb2dyYXBoaWNzLm9yZwpodHRwczovL2xp c3RzLmNhaXJvZ3JhcGhpY3Mub3JnL21haWxtYW4vbGlzdGluZm8vY2Fpcm8= --===============0990481595==--