| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
We might end up with a colormap with 0 entries, but whatever, it's a
colormap.
|
|
|
|
| |
Instead of poking into it directly.
|
|
|
|
|
|
|
|
| |
The weights could grow very large under certain circumstances, in
particular in security-relevant conditions, including the testsuite.
By allowing the weight allocation to fail, this can be worked around.
https://bugzilla.gnome.org/show_bug.cgi?id=754387
|
|
|
|
|
|
|
| |
The task thread function does not own a reference to the task
and thus should not unref it.
https://bugzilla.gnome.org/show_bug.cgi?id=755269
|
|
|
|
|
| |
Remove the static gdk-pixbuf-install property sheets as they are now
being completed during 'make dist'.
|
|
|
|
|
|
|
|
|
|
|
| |
This makes use of the common autotools modules that was just added so that
there would need to be less items in gdk-pixbuf's main Makefile.am, so that
we can generate the complete Visual Studio 2008/2010 project files (which
will then be used to obtain the Visual Studio 2012 and 2013 projects).
The other added benefit to this is that the property sheets used to install
headers will also make use of this mechanism so that the listing of public
headers can be kept up-to-date whenever the list of headers et updated.
|
|
|
|
|
|
|
|
|
|
|
| |
This adds a common autotools module that can be used by various
projects to generate the Visual Studio projects as needed, and
if necessary, generate the headers listings to "install" for that
project, based on items passed in to this. This is modelled on the
Makefile.introspection autotools file that is used by many GNOME
projects to generate the introspection files.
https://bugzilla.gnome.org/show_bug.cgi?id=721617
|
|
|
|
|
|
| |
Commit 8714ab4 introduced a GCCism by doing pointer arithmetic on a
gpointer, which is not allowed by other compilers. Fix that by
casting the pointer used in the addition.
|
|
|
|
|
|
|
| |
This "adds" projects for Visual Studio 2015 builds by doing what we
did before: copy the Visual Studio 2010 projects and replace items in
there as necessary, as the formats of the project files for Visual
Studio 2010, 2012, 2013 and 2015 are largely the same.
|
|
|
|
|
|
| |
b07c3bffffefb8573ad9ffcf926c07cb9f93d08b
https://bugzilla.gnome.org/show_bug.cgi?id=754154
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This is prone to segfaults when we are not careful.
|
|
|
|
|
| |
Same as before: don't do ptr = base + y * rowstride if y and
rowstride are integers.
|
|
|
|
| |
This file has not been compiled for a decade, at least.
|
|
|
|
| |
This is prone to segfaults when we are not careful.
|
|
|
|
|
|
|
| |
Same as before: don't do ptr = base + y * rowstride if y and
rowstride are integers.
This should fix http://bugzilla.gnome/org/753569
|
|
|
|
| |
This currently segfaults in the png loader.
|
|
|
|
|
|
| |
The scaling code had a similar problem to the one fixed in the
previous commit: Expressions like ptr = base + y * rowstride are
prone to overflow if y and rowstride are (possibly large) integers.
|
|
|
|
| |
Similar to the previous commit.
|
|
|
|
|
|
|
| |
The png loader was not careful enough in some places. Width * height
can overflow an integer.
This should fix http://bugzilla.gnome.org/734556.
|
|
|
|
|
|
|
|
| |
Make the custom malloc setup in this test work without the
no-longer-working g_mem_set_vtable, by overriding the weak
symbols for malloc, realloc, free directly. This will probably
only work with glibc, since we rely on the __libc- prefixed
versions of these functions.
|
|
|
|
|
| |
All the function in this source file are deprecated, and they
are using each other, so lets just ignore deprecations here.
|
|
|
|
|
|
|
|
|
| |
a55aa6eb introduced gdk_pixbuf_get_toplevel(), which is called if
GDK_PIXBUF_RELOCATABLE but is only built if USE_GMODULE &&
GDK_PIXBUF_RELOCATABLE. This causes build failures on MinGW and Darwin
when configured with --disable-modules.
https://bugzilla.gnome.org/show_bug.cgi?id=740912
|
|
|
|
|
|
|
| |
gcc realizes that the overflow checks aren't necessary. Why not?
Well, if an int overflows, the behavior is undefined. And turning on
-fomit-instructions is valid behavior in an undefined situation.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
n_weights is used to do overflow checks. So by reducing the size to 32
bits signed we overflow earlier. This is necessary because further down
the code lots of code uses int variables to iterate over this variable
and we don't want those to overflow.
The correct fix would be to make all those variables gsize too, but
that's way more invasive and requires different checks in different
places so I'm not gonna do that now.
And as long as scale factors are not expected to reach G_MAXINT it's not
really necessary to do this change anyway.
https://bugzilla.gnome.org/show_bug.cgi?id=753908
|
| |
|