mirror of
https://gitlab.freedesktop.org/cairo/cairo.git
synced 2025-12-24 10:10:11 +01:00
436c0c8be2
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/.
121 lines
4.1 KiB
C
121 lines
4.1 KiB
C
/*
|
|
* Copyright © 2004 Red Hat, Inc.
|
|
*
|
|
* 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
|
|
* Red Hat, Inc. not be used in advertising or publicity pertaining to
|
|
* distribution of the software without specific, written prior
|
|
* permission. Red Hat, Inc. makes no representations about the
|
|
* suitability of this software for any purpose. It is provided "as
|
|
* is" without express or implied warranty.
|
|
*
|
|
* RED HAT, INC. DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS
|
|
* SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND
|
|
* FITNESS, IN NO EVENT SHALL RED HAT, INC. 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: Carl D. Worth <cworth@cworth.org>
|
|
*/
|
|
|
|
/* Bug history
|
|
*
|
|
* 2004-11-04 Ned Konz <ned@squeakland.org>
|
|
*
|
|
* Reported bug on mailing list:
|
|
*
|
|
* From: Ned Konz <ned@squeakland.org>
|
|
* To: cairo@cairographics.org
|
|
* Date: Thu, 4 Nov 2004 09:49:38 -0800
|
|
* Subject: [cairo] getting assertions [cairo_cache.c:143: _entry_destroy:
|
|
* Assertion `cache->used_memory > entry->memory' failed]
|
|
*
|
|
* The attached program dies on me with the assert
|
|
*
|
|
* $ ./testCairo
|
|
* testCairo: cairo_cache.c:143: _entry_destroy: Assertion `cache->used_memory > entry->memory' failed.
|
|
*
|
|
* 2004-11-04 Carl Worth <cworth@cworth.org>
|
|
*
|
|
* I trimmed down Ned's example to the folllowing test while still
|
|
* maintaining the assertion.
|
|
*
|
|
* Oh, actually, it looks like I may have triggered something
|
|
* slightly different:
|
|
*
|
|
* text_cache_crash: cairo_cache.c:422: _cairo_cache_lookup: Assertion `cache->max_memory >= (cache->used_memory + new_entry->memory)' failed.
|
|
*
|
|
* I'll have to go back and try the original test after I fix this.
|
|
*
|
|
* 2004-11-13 Carl Worth <cworth@cworth.org>
|
|
*
|
|
* Found the bug. cairo_gstate_select_font was noticing when the
|
|
* same font was selected twice in a row and was erroneously failing
|
|
* to free the old reference. Committed a fix and verified it also
|
|
* fixed the original test case.
|
|
*/
|
|
|
|
#include "cairo-test.h"
|
|
|
|
static cairo_test_draw_function_t draw;
|
|
|
|
static const cairo_test_t test = {
|
|
"text-cache-crash",
|
|
"Test case for bug causing an assertion failure in _cairo_cache_lookup",
|
|
0, 0,
|
|
draw
|
|
};
|
|
#include <cairo.h>
|
|
|
|
static cairo_test_status_t
|
|
draw (cairo_t *cr, int width, int height)
|
|
{
|
|
/* Once there was a bug that choked when selecting the same font twice. */
|
|
cairo_select_font_face (cr, "sans",
|
|
CAIRO_FONT_SLANT_NORMAL, CAIRO_FONT_WEIGHT_BOLD);
|
|
cairo_set_font_size (cr, 40.0);
|
|
|
|
cairo_select_font_face (cr, "sans",
|
|
CAIRO_FONT_SLANT_NORMAL, CAIRO_FONT_WEIGHT_BOLD);
|
|
cairo_set_font_size (cr, 40.0);
|
|
cairo_move_to (cr, 10, 50);
|
|
cairo_show_text (cr, "hello");
|
|
|
|
/* Then there was a bug that choked when selecting a font too big
|
|
* for the cache. */
|
|
|
|
/* XXX: Sometimes this leads to an assertion:
|
|
|
|
_cairo_cache_lookup: Assertion `cache->max_memory >= (cache->used_memory + new_entry->memory)' failed.
|
|
Aborted
|
|
|
|
But other times my machine hangs completely only to return to life
|
|
several minutes later with some programs missing. This seems like
|
|
the out-of-memory killer to me.
|
|
|
|
It seems like I usually get the assertion when I run
|
|
./text_cache_crash directly and I usually get the machine hang when
|
|
I run "make check" but I don't know if there's a perfect
|
|
correlation there.
|
|
|
|
So there's a bad bug here somewhere that really needs to be fixed.
|
|
But in the meantime, I need "make check" not to destory work, so
|
|
I'm commenting this test out for now.
|
|
|
|
cairo_set_font_size (cr, 500);
|
|
cairo_show_text (cr, "hello");
|
|
*/
|
|
|
|
return CAIRO_TEST_SUCCESS;
|
|
}
|
|
|
|
int
|
|
main (void)
|
|
{
|
|
return cairo_test (&test);
|
|
}
|