Library Name | libdmtx |
---|---|
Version #1 | 0.5.1 |
Version #2 | 0.5.2 |
CPU Type | x86 |
GCC Version | 4.6.1 |
Total Header Files | 1 |
---|---|
Total Shared Libraries | 1 |
Total Symbols / Types | 70 / 66 |
Verdict | Incompatible (16.4%) |
Severity | Count | |
---|---|---|
Added Symbols | - | 9 |
Removed Symbols | High | 3 |
Problems with Data Types | High | 1 |
Medium | 21 | |
Low | 16 | |
Problems with Symbols | High | 2 |
Medium | 8 | |
Low | 3 | |
Problems with Constants | Low | 0 |
Other Changes in Constants | - | 9 |
Change | Effect | |
---|---|---|
1 | Size of this type has been changed from 8 bytes to 12 bytes. | Layout of parameter's stack of several functions has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | Parameter x of type int has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
2 | 2nd middle parameter dir has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | Field edgeDir has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
2 | Field scanDir has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
Change | Effect | |
---|---|---|
1 | Size of field grid has been changed from 48 bytes to 64 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
Change | Effect | |
---|---|---|
1 | Field heightScaled has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
2 | Field scale has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
3 | Field widthScaled has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
4 | Field xMax has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
5 | Field xMaxScaled has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
6 | Field xMin has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
7 | Field xMinScaled has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
8 | Field yMax has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
9 | Field yMaxScaled has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
10 | Field yMin has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
11 | Field yMinScaled has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
12 | The relative position of field height has been changed from 2 to 1. | Applications will access incorrect memory when attempting to access this field. |
13 | The relative position of field pageCount has been changed from 0 to 2. | Applications will access incorrect memory when attempting to access this field. |
14 | The relative position of field width has been changed from 1 to 0. | Applications will access incorrect memory when attempting to access this field. |
Change | Effect | |
---|---|---|
1 | Field xMax has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
2 | Field xMin has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
3 | Field yMax has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
4 | Field yMin has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
Change | Effect | |
---|---|---|
1 | Type of return value has been changed from int to double. | The return value became passed in different register. Applications will read the wrong memory block instead of the return value. Also, distribution of parameters on the available registers and stack may be changed. |
Change | Effect | |
---|---|---|
1 | Base type of 1st parameter dec has been changed from struct DmtxDecode_struct (52 bytes) to struct DmtxImage_struct (64 bytes). | This parameter may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | Base type of 1st parameter dec has been changed from struct DmtxDecode_struct (52 bytes) to struct DmtxImage_struct (64 bytes). | This parameter may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | 4th parameter gap has been removed from the calling stack. | This parameter will be ignored by the function. |
2 | Parameter p0 of type DmtxPixelLoc has been removed from the calling stack. | This parameter will be ignored by the function. |
3 | Parameter p1 of type DmtxPixelLoc has been removed from the calling stack. | This parameter will be ignored by the function. |
Change | Effect | |
---|---|---|
1 | 4th parameter offset has been removed from the calling stack. | This parameter will be ignored by the function. |
Change | Effect | |
---|---|---|
1 | Type of return value has been changed from int to double. | The return value became passed in different register. Applications will read the wrong memory block instead of the return value. Also, distribution of parameters on the available registers and stack may be changed. |
Change | Effect | |
---|---|---|
1 | Size of this type has been changed from 44 bytes to 36 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
2 | Field maxDirAll has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
3 | Field maxDirOrtho has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
4 | Field assigned has been renamed to dirsTested. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
Change | Effect | |
---|---|---|
1 | Field edgeThresh has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
2 | Field scanGap has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
3 | Field shrinkMax has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
4 | Field shrinkMin has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
5 | Field squareDevn has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
6 | Size of this type has been changed from 52 bytes to 92 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Size of this type has been changed from 20 bytes to 64 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
2 | Type of field height has been changed from unsigned int to int. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
3 | Type of field pageCount has been changed from unsigned int to int. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
4 | Type of field width has been changed from unsigned int to int. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
Change | Effect | |
---|---|---|
1 | Field status has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
Change | Effect | |
---|---|---|
1 | Size of this type has been changed from 48 bytes to 64 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | 1st parameter dec has been renamed to img. | Renaming of a parameter may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | 1st parameter dec has been renamed to img. | Renaming of a parameter may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | 3rd parameter lineNbr has been renamed to y. | Renaming of a parameter may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | The constant DMTX_FALSE with value 0 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant DMTX_MODULE_ON with value 0x07 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant DMTX_REGION_DROPPED_1ST with value 5 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant DMTX_REGION_DROPPED_2ND with value 6 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant DMTX_REGION_DROPPED_EDGE with value 4 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant DMTX_REGION_DROPPED_RIGHT with value 7 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant DMTX_REGION_DROPPED_SIZE with value 9 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant DMTX_REGION_DROPPED_TOP with value 8 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant DMTX_TRUE with value 1 has been added. | No effect. |