Library Name | libmtp |
---|---|
Version #1 | 0.0.8 |
Version #2 | 0.0.9 |
CPU Architecture | x86 |
GCC Version | 4.6.1 |
Total Header Files | 1 |
---|---|
Total Shared Libraries | 1 |
Total Symbols / Types | 52 / 60 |
Verdict | Incompatible (19.23%) |
Severity | Count | |
---|---|---|
Added Symbols | - | 12 |
Removed Symbols | High | 1 |
Problems with Data Types | High | 0 |
Medium | 28 | |
Low | 11 | |
Problems with Symbols | High | 1 |
Medium | 0 | |
Low | 31 | |
Problems with Constants | Low | 0 |
Other Changes | - | 1 |
Change | Effect | |
---|---|---|
1 | Type of 5th parameter p5 has been changed from int (4 bytes) to uint8_t const (1 byte). | 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 | Value of member LIBMTP_FILETYPE_ASF has been changed from 9 to 10. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
2 | Value of member LIBMTP_FILETYPE_AVI has been changed from 7 to 8. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
3 | Value of member LIBMTP_FILETYPE_BMP has been changed from 15 to 16. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
4 | Value of member LIBMTP_FILETYPE_GIF has been changed from 16 to 17. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
5 | Value of member LIBMTP_FILETYPE_HTML has been changed from 26 to 27. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
6 | Value of member LIBMTP_FILETYPE_JFIF has been changed from 13 to 14. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
7 | Value of member LIBMTP_FILETYPE_JPEG has been changed from 12 to 13. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
8 | Value of member LIBMTP_FILETYPE_MP4 has been changed from 4 to 5. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
9 | Value of member LIBMTP_FILETYPE_MPEG has been changed from 8 to 9. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
10 | Value of member LIBMTP_FILETYPE_PICT has been changed from 17 to 18. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
11 | Value of member LIBMTP_FILETYPE_PNG has been changed from 18 to 19. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
12 | Value of member LIBMTP_FILETYPE_QT has been changed from 10 to 11. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
13 | Value of member LIBMTP_FILETYPE_TEXT has been changed from 25 to 26. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
14 | Value of member LIBMTP_FILETYPE_TIFF has been changed from 14 to 15. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
15 | Value of member LIBMTP_FILETYPE_UNDEF_AUDIO has been changed from 5 to 6. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
16 | Value of member LIBMTP_FILETYPE_UNDEF_VIDEO has been changed from 11 to 12. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
17 | Value of member LIBMTP_FILETYPE_UNKNOWN has been changed from 27 to 28. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
18 | Value of member LIBMTP_FILETYPE_VCARD2 has been changed from 21 to 22. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
19 | Value of member LIBMTP_FILETYPE_VCARD3 has been changed from 22 to 23. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
20 | Value of member LIBMTP_FILETYPE_WINDOWSIMAGEFORMAT has been changed from 23 to 24. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
21 | Value of member LIBMTP_FILETYPE_WINEXEC has been changed from 24 to 25. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
22 | Value of member LIBMTP_FILETYPE_WMV has been changed from 6 to 7. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
Change | Effect | |
---|---|---|
1 | Field bitrate 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 bitratetype 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 nochannels 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 samplerate 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 usecount 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 wavecodec 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 | Value of member LIBMTP_FILETYPE_VCALENDAR1 has been changed from 19 to 20. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
2 | Value of member LIBMTP_FILETYPE_VCALENDAR2 has been changed from 20 to 21. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
Change | Effect | |
---|---|---|
1 | Field default_music_folder has been added to this type. | 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 default_organizer_folder has been added to this type. | 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 default_picture_folder has been added to this type. | 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 default_playlist_folder has been added to this type. | 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 default_video_folder has been added to this type. | 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 | Field default_zencast_folder has been added to this type. | 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. |
7 | Size of this type has been changed from 20 bytes to 44 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 52 bytes to 76 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
2 | Field rating has been added to this type. | 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 | Type of 2nd parameter p2 has been changed from uint32_t to uint32_t const. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 2nd parameter p2 has been changed from uint32_t to uint32_t const. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 2nd parameter p2 has been changed from uint32_t to uint32_t const. | Replacement of parameter data type may indicate a change in its semantic meaning. |
2 | Type of 3rd parameter p3 has been changed from uint32_t to uint32_t const. | Replacement of parameter data type may indicate a change in its semantic meaning. |
3 | Type of 4th parameter p4 has been changed from char to uint8_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 2nd parameter p2 has been changed from uint32_t to uint32_t const. | Replacement of parameter data type may indicate a change in its semantic meaning. |
2 | Type of 3rd parameter p3 has been changed from uint32_t to uint32_t const. | Replacement of parameter data type may indicate a change in its semantic meaning. |
3 | Type of 4th parameter p4 has been changed from uint16_t to uint16_t const. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 2nd parameter p2 has been changed from uint32_t to uint32_t const. | Replacement of parameter data type may indicate a change in its semantic meaning. |
2 | Type of 3rd parameter p3 has been changed from uint32_t to uint32_t const. | Replacement of parameter data type may indicate a change in its semantic meaning. |
3 | Type of 4th parameter p4 has been changed from uint32_t to uint32_t const. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 1st parameter p1 has been changed from char* to char const*const. | Replacement of parameter data type may indicate a change in its semantic meaning. |
2 | Type of 3rd parameter p3 has been changed from uint16_t to uint16_t const. | Replacement of parameter data type may indicate a change in its semantic meaning. |
3 | Type of 4th parameter p4 has been changed from void* to void const*const. | Replacement of parameter data type may indicate a change in its semantic meaning. |
4 | Type of 5th parameter p5 has been changed from void* to void const*const. | Replacement of parameter data type may indicate a change in its semantic meaning. |
5 | Type of 6th parameter p6 has been changed from void* to void const*const. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 2nd parameter p2 has been changed from void* to void const*const. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 2nd parameter p2 has been changed from void* to void const*const. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 2nd parameter p2 has been changed from void* to void const*const. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 2nd parameter p2 has been changed from uint32_t to uint32_t const. | Replacement of parameter data type may indicate a change in its semantic meaning. |
2 | Type of 3rd parameter p3 has been changed from uint32_t* to uint32_t const*const. | Replacement of parameter data type may indicate a change in its semantic meaning. |
3 | Type of 4th parameter p4 has been changed from uint32_t to uint32_t const. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 2nd parameter p2 has been changed from uint32_t to uint32_t const. | Replacement of parameter data type may indicate a change in its semantic meaning. |
2 | Type of 3rd parameter p3 has been changed from uint32_t to uint32_t const. | Replacement of parameter data type may indicate a change in its semantic meaning. |
3 | Type of 4th parameter p4 has been changed from char* to char const*const. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 2nd parameter p2 has been changed from uint32_t to uint32_t const. | Replacement of parameter data type may indicate a change in its semantic meaning. |
2 | Type of 3rd parameter p3 has been changed from uint32_t to uint32_t const. | Replacement of parameter data type may indicate a change in its semantic meaning. |
3 | Type of 4th parameter p4 has been changed from uint16_t to uint16_t const. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 2nd parameter p2 has been changed from uint32_t to uint32_t const. | Replacement of parameter data type may indicate a change in its semantic meaning. |
2 | Type of 3rd parameter p3 has been changed from uint32_t to uint32_t const. | Replacement of parameter data type may indicate a change in its semantic meaning. |
3 | Type of 4th parameter p4 has been changed from uint32_t to uint32_t const. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | The member LIBMTP_FILETYPE_AUDIBLE with value 4 has been added. | No effect. |