| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
This makes it easier to find them and reference them.
|
|
|
|
|
|
|
|
|
|
|
| |
This could happen if something in the test fails, so this allows early
diagnosis of problems. It also hints to Coverity that the loops which
follow can’t run (almost) infinitely due to the loop bounds being
inverted.
Coverity IDs: 1391987, 1399712
https://bugzilla.gnome.org/show_bug.cgi?id=778943
|
|
|
|
|
|
|
|
|
|
|
| |
The code is correct (the line buffer is set when DecodeHeader() returns
successfully with a non-zero-length line), but that’s not at all obvious
from the code, and is tripping Coverity up. Add an assertion to make it
clearer.
Coverity ID: 1400057
https://bugzilla.gnome.org/show_bug.cgi?id=778943
|
|
|
|
| |
So we can dist from Autotools, and build with Meson from the tarball.
|
|
|
|
|
| |
We want to be able to run the gdk-pixbuf tests after installing them in
a known system location, especially when running CI.
|
|
|
|
|
| |
We need to go through an intermediate script in order to generate the
thumbnailer's desktop file.
|
| |
|
|
|
|
| |
Contributed library.
|
|
|
|
| |
Both API reference and man pages.
|
|
|
|
|
|
|
| |
Just like the Autotools build does.
We also provide a simple escape hatch for platforms where building
introspection data is too complicated at the moment.
|
|
|
|
|
| |
The name is `gdk_pixbuf-2.0`, not `gdk-pixbuf-2.0`, I guess for
historical reasons.
|
|
|
|
| |
It was lost in the port.
|
|
|
|
|
|
| |
Commit 591f959adb0d1f85a869dfc14b9b21a0de8417eb moved to including the
header, instead of including the source. This means that we need to
build the source, in order to get the marshallers.
|
|
|
|
|
|
|
|
|
| |
We depend on C99 functions in the math library; if the math library is
not found, or if it's not C99-compliant, we have fallbacks in place.
Commit 68da550e817b1269d1ccfdeeec2a53ddbd7b920a removed the checks, and
we ended up compiling the fallbacks even when the C library provided
these symbols — leading to a build error caught by Continuous.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Meson is a better build system than Autotools that has gotten traction
in the GNOME community.
The build is pretty much equivalent between Autotools and Meson, but at
this point it needs further testing to verify complete matching
behaviour.
The GDI-plus loaders are not currently built, as that will require
access to a platform I don't have in order to test them.
Additionally, the API reference is not being generated yet in Meson.
|
|
|
|
|
|
| |
The uninstalled pkg-config file is generally considered pointless;
building multiple modules should not look into source directories of
the dependencies, but use a separate installation prefix.
|
|
|
|
| |
Don't leave files behind.
|
|
|
|
|
| |
Do not include the source, otherwise we're going to compile symbols
twice.
|
| |
|
|
|
|
|
| |
Windows will not be using GIO to do mime-sniffing, but it's a
requirement on other platforms.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Use AC_CHECK_LIBM to check for the math library. This
should also cover BeOS if necessary.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=780667
|
|
|
|
|
|
| |
File created using afl.
https://bugzilla.gnome.org/show_bug.cgi?id=777315
|
|
|
|
|
|
|
|
|
| |
Avoid allocating nearly 6 gigs of data when parsing the CVE-2015-4491
test only to free it when we've calculated that the rowstride * height
would overflow by calculating the rowstride before doing the allocation,
using the new gdk_pixbuf_calculate_rowstride() helper.
https://bugzilla.gnome.org/show_bug.cgi?id=765094
|
|
|
|
|
|
| |
To calculate the rowstride without allocating memory!
https://bugzilla.gnome.org/show_bug.cgi?id=765094
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
The loader should return an error in that case.
https://bugzilla.gnome.org/show_bug.cgi?id=778204
|
|
|
|
|
|
|
|
| |
If we don't even read enough data to fill the header, return an
error. This doesn't cover everything that could go wrong with
the ICO incremental loader, but this is a good first throw.
https://bugzilla.gnome.org/show_bug.cgi?id=778204
|
|
|
|
|
|
|
|
| |
If the loader returns a NULL pixbuf without returning an
error, the skeleton would crash trying to print the error.
Print that the thumbnailer is broken instead.
https://bugzilla.gnome.org/show_bug.cgi?id=778204
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=783538
|
|
|
|
|
|
|
|
|
| |
The rowstride is stored as an int, and is an int in the public API.
Making it an unsigned int for those calculations would increase
the limit, which would obviously cause problems when the calculated
value ends up between G_MAXUINT and G_MAXINT in the positives.
https://bugzilla.gnome.org/show_bug.cgi?id=765094
|
| |
|
|
|
|
|
|
|
| |
Originally from the JPEG conformance tests:
http://people.sc.fsu.edu/~jburkardt/data/jpg/jpg.html
https://bugzilla.gnome.org/show_bug.cgi?id=785171
|
|
|
|
|
|
|
|
|
|
| |
Commit c2a40a92fe3df4111ed9da51fe3368c079b86926 restricts the jpeg
loader to files with 3 or 4 color components.
Also allow JCS_GRAYSCALE images with only 1 color component.
These grayscale images are supported through explode_gray_into_buf.
https://bugzilla.gnome.org/show_bug.cgi?id=785171
|
| |
|
|
|
|
|
|
| |
The sanity checks for image dimensions have since been tightened in
commit 4154d4f and we should not be able to open this huge image anymore
as the dimensions exceed what's possible.
|
|
|
|
|
|
|
| |
The rowstride *could* be negative if the pixbuf is invalid. Check that
it is valid before using it to sanity check the image's dimensions.
See https://bugzilla.gnome.org/show_bug.cgi?id=776694
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=785447
|
|
|
|
|
|
|
| |
Despite the inherited comment, commit 99508c7 sorted the icons by
increasing instead of decreasing quality.
https://bugzilla.gnome.org/show_bug.cgi?id=785447
|