According to the X11 protocol specification, "The visual type must be one supported by the screen (or a Match error results)."
It does not say anything about invalid visual IDs causing Value errors. Reported-by: Nalluri Harikrishna <[email protected]> Reported-by: Rahul Singhal <[email protected]> Signed-off-by: Aaron Plattner <[email protected]> --- xts5/Xlib7/XCreateColormap.m | 8 ++++---- 1 files changed, 4 insertions(+), 4 deletions(-) diff --git a/xts5/Xlib7/XCreateColormap.m b/xts5/Xlib7/XCreateColormap.m index 272b6f0..ec825b1 100644 --- a/xts5/Xlib7/XCreateColormap.m +++ b/xts5/Xlib7/XCreateColormap.m @@ -600,20 +600,20 @@ error occurs. >>ASSERTION Bad A When xname is called with an invalid visual, then a -.S BadValue +.S BadMatch error occurs. >>STRATEGY Make a visual structure invalid using badvis. Create a colourmap for this visual with XCreateColorMap. -Verify that a BadValue error occurred. ->>CODE BadValue +Verify that a BadMatch error occurred. +>>CODE BadMatch Visual vi; alloc = AllocNone; badvis(&vi); visual = &vi; XCALL; - if(geterr() == BadValue) + if(geterr() == BadMatch) PASS; >>ASSERTION Bad A .ER BadWindow -- 1.7.4.1 _______________________________________________ [email protected]: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
