Hi, would be it be reasonable to mark GLib 1.2 and packages depending on it as dangerous/problematic/whatever for non-32-bit systems? GLib 1.2 is deprecated according to the GLib developers, so nobody should be using it anymore anyway. There are many size_t vs. int issues in GLib 1.2. For example, see g_string_append() in gstring.c and note that gsize is not an alias of size_t but blatantly hardcoded to an unsigned 32-bit integer type in glib.h. Thus, on a 64-bit machine with more than 2 GiB memory it's very easy to trigger stack and heap overflows. GLib 2.0 cannot be used as a drop-in replacement - prototypes but also the semantics of a few functions have changed but it's usually easy to port them to it. The same applies to software depending on Gtk+ 1.2. -- Christian
Attachment:
pgpPyaqylLiLw.pgp
Description: PGP signature