From: Sam James <sam@gentoo.org>
To: distributions@lists.linux.dev
Subject: Breakage with glib-2.76.0 (exposes bugs in buggy packages)
Date: Fri, 17 Mar 2023 14:00:43 +0000 [thread overview]
Message-ID: <87pm97325m.fsf@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1098 bytes --]
Hi folks,
glib-2.76 switches from using its own 'slice' allocator to using
the system malloc instead.
This ends up exposing various memory safety bugs in consumers
of glib, including some XFCE software.
So far:
- openbox (https://bugzilla.icculus.org/show_bug.cgi?id=6669)
- xfce4-session (https://gitlab.xfce.org/xfce/xfce4-session/-/issues/166)
- xfce4-screensaver (https://gitlab.xfce.org/apps/xfce4-screensaver/-/issues/119)
- thunar (https://gitlab.xfce.org/xfce/thunar/-/issues/1063)
- gegl (https://gitlab.gnome.org/GNOME/gegl/-/issues/320)
- girara (https://git.pwmt.org/pwmt/girara/-/issues/17)
- tint2 (not yet reported upstream, https://bugs.gentoo.org/901775)
See also:
-
https://bugs.gentoo.org/showdependencytree.cgi?id=901805&hide_resolved=0
- https://gitlab.gnome.org/GNOME/glib/-/issues/2937
- https://gitlab.gnome.org/GNOME/glib/-/issues/2941
You can try see these issues with older glib by using Valgrind (which
makes glib on older versions disable the slice allocator) or ASAN.
I anticipate there'll be quite a few more of these.
best,
sam
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 377 bytes --]
next reply other threads:[~2023-03-17 14:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 14:00 Sam James [this message]
2023-03-17 14:29 ` Breakage with glib-2.76.0 (exposes bugs in buggy packages) Sam James
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pm97325m.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=distributions@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).