XCB_DESTROY_NOTIFY & SIGTERM

[Peter Harris]

>  Hoping to clarify or ensure that a xcb_generic_error_t error_code of
> 143 is a SIGTERM code. First time I received this and a non-xcb source claims this
> is so.

No, signals are in a different namespace from X11 error codes.

Errors >= 128 are "extension errors", which are allocated dynamically. On my server, for example, 143 would be RENDER + 3, which is "BadGlyphSet"

 https://gitlab.freedesktop.org/xorg/proto/xcbproto/-/blob/master/src/render.xml?ref_type=heads#L138

BadGlyphSet probably isn't the error you are getting, you will have to check the extension error numbers of your server. From the command line, you can use "xdpyinfo -queryExt" to see the base error number of each extension. Programmatically, you can call xcb_get_extension_data for each of the extensions you used to find the relevant base error numbers.

Peter Harris
================================
Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ Main Office Toll Free Number: +1 855.577.4323
Contact Customer Support: https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport
Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - http://www.rocketsoftware.com/manage-your-email-preferences
Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy
================================

This communication and any attachments may contain confidential information of Rocket Software, Inc. All unauthorized use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify Rocket Software immediately and destroy all copies of this communication. Thank you.