Library Name | libmemcached |
---|---|
Version #1 | 0.8 |
Version #2 | 0.9 |
CPU Type | x86 |
GCC Version | 4.6.1 |
Total Header Files | 1 |
---|---|
Total Shared Libraries | 1 |
Total Symbols / Types | 35 / 39 |
Verdict | Incompatible (92.9%) |
Severity | Count | |
---|---|---|
Added Symbols | - | 4 |
Removed Symbols | High | 0 |
Problems with Data Types | High | 5 |
Medium | 8 | |
Low | 7 | |
Problems with Symbols | High | 0 |
Medium | 2 | |
Low | 0 | |
Problems with Constants | Low | 0 |
Other Changes in Data Types | - | 1 |
Change | Effect | |
---|---|---|
1 | Field read_buffer has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 read_buffer_length has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 read_ptr has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 write_buffer has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 write_buffer_offset has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 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 | Field read_buffer 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 read_buffer_length 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 read_ptr 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 servAddr 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 write_buffer 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 write_buffer_offset 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 write_ptr 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 field version has been changed from char[8] (8 bytes) to char[12] (12 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
Change | Effect | |
---|---|---|
1 | Base type of 5th parameter value has been changed from unsigned int (4 bytes) to unsigned long long (8 bytes). | This parameter may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | Base type of 5th parameter value has been changed from unsigned int (4 bytes) to unsigned long long (8 bytes). | This parameter may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | Value of member MEMCACHED_MAXIMUM_RETURN has been changed from 28 to 29. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
Change | Effect | |
---|---|---|
1 | Field major_version 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 minor_version 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 | Size of this type has been changed from 24 bytes to 16452 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
4 | Field micro_version 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. |
Change | Effect | |
---|---|---|
1 | Size of this type has been changed from 16476 bytes to 72 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 140 bytes to 144 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | The member MEMCACHED_NO_KEY_PROVIDED with value 28 has been added. | No effect. |