Querying XOP error codes

Share icon

Wed, 08/31/2016 - 05:47 pm

I'm writing an XOP where I've added a few error codes with

<br />
#define OLD_IGOR                   1 + FIRST_XOP_ERR<br />
#define UNHANDLED_CPP_EXCEPTION    2 + FIRST_XOP_ERR<br />
...<br />


Now when I test the XOP I wanted to check some of these errors.
But the exact numeric values are unexpected.

For example UNHANDLED_CPP_EXCEPTION is 196610.

My questions:
- Is the exact number always constant or does it depend on the number of custom XOPs I've installed? (I'd expect the latter)
- Is there a way to translate the error code values reliably and with standard tools?
- Any suggestions as alternative testing methods?

Thanks,
Thomas
Quote:
Is the exact number always constant or does it depend on the number of custom XOPs I've installed

It depends on the order of loading XOPs.

Quote:
Any suggestions as alternative testing methods?


I'm not sure, but I believe that, if you AND with 0xFFFF and add FIRST_XOP_ERR, you will get your error code. This is an implementation detail and subject to change.

Also, if you pass the code (e.g, 196610, which is 0x30002) to GetErrMessage, you should get your error string.

August 31, 2016 at 08:03 pm - Permalink