cairo/test/big-trap.c
Chris Wilson 436c0c8be2 [test] Preparatory work for running under memfault.
In order to run under memfault, the framework is first extended to handle
running concurrent tests - i.e. multi-threading. (Not that this is a
requirement for memfault, instead it shares a common goal of storing
per-test data).  To that end all the global data is moved into a per-test
context and the targets are adjusted to avoid overlap on shared, global
resources (such as output files and frame buffers). In order to preserve
the simplicity of the standard draw routines, the context is not passed
explicitly as a parameter to the routines, but is instead attached to the
cairo_t via the user_data.

For the masochist, to enable the tests to be run across multiple threads
simply set the environment variable CAIRO_TEST_NUM_THREADS to the desired
number.

In the long run, we can hope the need for memfault (runtime testing of
error paths) will be mitigated by static analysis. A promising candidate
for this task would appear to be http://hal.cs.berkeley.edu/cil/.
2008-08-13 21:54:59 +01:00

94 lines
3.5 KiB
C

/*
* Copyright © 2006 Mozilla Corporation
*
* Permission to use, copy, modify, distribute, and sell this software
* and its documentation for any purpose is hereby granted without
* fee, provided that the above copyright notice appear in all copies
* and that both that copyright notice and this permission notice
* appear in supporting documentation, and that the name of
* Mozilla Corporation not be used in advertising or publicity pertaining to
* distribution of the software without specific, written prior
* permission. Mozilla Corporation makes no representations about the
* suitability of this software for any purpose. It is provided "as
* is" without express or implied warranty.
*
* MOZILLA CORPORATION DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS
* SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND
* FITNESS, IN NO EVENT SHALL MOZILLA CORPORATION BE LIABLE FOR ANY SPECIAL,
* INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER
* RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION
* OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR
* IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
*
* Author: Vladimir Vukicevic <vladimir@pobox.com>
*/
#include "cairo-test.h"
static cairo_test_draw_function_t draw;
/* This test was originally written to exercise a bug in pixman in
* which it would scribble all over memory when given a particular
* (and bogus) trapezoid. However, a recent change to
* _cairo_fixed_from_double changed the details of the bogus trapezoid
* (it overflows in a different way now), so the bug is being masked.
*
* According to Vladimir, (http://lists.freedesktop.org/archives/cairo/2006-November/008482.html):
*
* Before the change, the two trapezoids that were generated were:
*
* Trap[0]: T: 0x80000000 B: 0x80000003
* L: [(0x000a0000, 0x80000000) (0x00080000, 0x00080000)]
* R: [(0x01360000, 0x80000000) (0x01380000, 0x00080000)]
* Trap[1]: T: 0x80000003 B: 0x00080000
* L: [(0x000a0000, 0x80000000) (0x00080000, 0x00080000)]
* R: [(0x01360000, 0x80000000) (0x01380000, 0x00080000)]
*
* After the change, the L/R coordinates are identical for both traps, but
* the top and bottom change:
*
* Trap[0]: t: 0x80000000 b: 0xfda80003
* l: [(0x000a0000, 0x80000000) (0x00080000, 0x00080000)]
* r: [(0x01360000, 0x80000000) (0x01380000, 0x00080000)]
* Trap[1]: t: 0xfda80003 b: 0x00080000
* l: [(0x000a0000, 0x80000000) (0x00080000, 0x00080000)]
* r: [(0x01360000, 0x80000000) (0x01380000, 0x00080000)]
*
* I think the fix we want here is to rewrite this test to call
* directly into pixman with the trapezoid of interest, (which will
* require adding a new way to configure cairo for "testing" which
* will prevent the hiding of internal library symbols.
*/
static const cairo_test_t test = {
"big-trap",
"Test oversize trapezoid with a clip region"
"\nTest needs to be adjusted to trigger the original bug",
100, 100,
draw
};
static cairo_test_status_t
draw (cairo_t *cr, int width, int height)
{
/* Note that without the clip, this doesn't crash... */
cairo_new_path (cr);
cairo_rectangle (cr, 0, 0, width, height);
cairo_clip (cr);
cairo_new_path (cr);
cairo_line_to (cr, 8.0, 8.0);
cairo_line_to (cr, 312.0, 8.0);
cairo_line_to (cr, 310.0, 31378756.2666666666);
cairo_line_to (cr, 10.0, 31378756.2666666666);
cairo_line_to (cr, 8.0, 8.0);
cairo_fill (cr);
return CAIRO_TEST_SUCCESS;
}
int
main (void)
{
return cairo_test (&test);
}