[cairo] ASSERT_NOT_REACHED

Carl Worth cworth at cworth.org
Tue Jul 19 07:35:24 PDT 2005


On Tue, 19 Jul 2005 07:29:46 -0700, Radek Doulík wrote:
> As Carl suggested on irc, some code was using cairo_format_t at place
> where cairo_content_t was expected (API changed lately).

Yes, but there's still something wrong. An application error, (such as
passing a cairo_format_t instead of a cairo_content_t), should never
cause an assertion. The assertion triggering is intended to indicate
that there is some internal error within cairo itself.

For example, in the case of cairo_surface_create_similar, the
CAIRO_CONTENT_VALID check should trigger before it ever gets the
chance to get to the assertion.

So I would still like to hear more specifics (eg. stack trace leading
to assertion) from users who are seeing this problem so that we can
fix whatever bug it is that cairo has.

-Carl
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.freedesktop.org/archives/cairo/attachments/20050719/bed68d82/attachment.pgp


More information about the cairo mailing list