Total header files | 51 |
Total shared objects | 4 |
Total interfaces / types | 98 / 31 |
Verdict | Incompatible |
Added interfaces | 5 | |
Withdrawn interfaces | 0 | |
Problems in Data Types | High risk | 0 |
Medium risk | 63 | |
Low risk | 48 | |
Interface problems | High risk | 107 |
Medium risk | 0 | |
Low risk | 0 | |
Constant Problems | 0 |
Incompatibility | Effect | |
1 | Member recv_size has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
2 | Member send_size has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
3 | Member sasl has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
4 | Member get_key_failure has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
5 | Member options has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
6 | Member rcv_timeout has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
7 | Member on_clone has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
8 | Member number_of_replicas has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
9 | Member server_failure_limit has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
10 | Member io_bytes_watermark has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
11 | Member number_of_hosts has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
12 | Member prefix_key has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
13 | Member io_key_prefetch has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
14 | Member continuum_points_counter has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
15 | Member result has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
16 | Member servers has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
17 | Member continuum has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
18 | Member on_cleanup has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
19 | Member poll_timeout has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
20 | Member flags has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
21 | Member callbacks has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
22 | Member snd_timeout has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
23 | Member continuum_count has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
24 | Member distribution_hashkit has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
25 | Member retry_timeout has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
26 | Member next_distribution_rebuild has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
27 | Member last_disconnected_server has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
28 | Member delete_trigger has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
29 | Member io_msg_watermark has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
30 | Member distribution has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
31 | Member prefix_key_length has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
32 | Member hashkit has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
33 | Member connect_timeout has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
34 | Member allocators has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
35 | Member cached_errno has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
36 | Member tcp_keepidle has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
37 | Member user_data has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
Incompatibility | Effect | |
1 | Member major_version has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
2 | Member io_wait_count has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
3 | Member hostname has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
4 | Member write_buffer has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
5 | Member number_of_hosts has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
6 | Member next_retry has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
7 | Member limit_maxbytes has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
8 | Member address_info has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
9 | Member read_buffer has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
10 | Member read_buffer_length has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
11 | Member micro_version has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
12 | Member io_bytes_sent has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
13 | Member cached_server_error has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
14 | Member weight has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
15 | Member port has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
16 | Member read_ptr has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
17 | Member state has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
18 | Member fd has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
19 | Member type has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
20 | Member minor_version has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
21 | Member read_data_length has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
22 | Member cached_errno has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
23 | Member write_buffer_offset has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
24 | Member cursor_active has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
25 | Member server_failure_counter has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
26 | Member root has been withdrawn from this type. | 1) Applications will access incorrect memory when attempting to access this member. 2) The size of the inclusive type will also be affected. |
Incompatibility | Effect | |
1 | Member interface has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
2 | Member post_execute has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
3 | Member unknown has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
4 | Member pre_execute has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
Incompatibility | Effect | |
1 | Member flags has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
2 | Member options has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
3 | Member distribution_hash has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
Incompatibility | Effect | |
1 | Member context has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
Incompatibility | Effect | |
1 | Member is_processing_input has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
2 | Member is_time_for_rebuild has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
Incompatibility | Effect | |
1 | Size of this type has been changed from 776 to 696 bytes. | Change of type size may lead to different effects in different contexts. [+] ... |
Incompatibility | Effect | |
1 | Member value has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
2 | Member item_key has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
3 | Member item_expiration has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
4 | Member options has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
5 | Member item_cas has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
6 | Member root has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
7 | Member key_length has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
Incompatibility | Effect | |
1 | Member context has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
2 | Member proc has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
Incompatibility | Effect | |
1 | Member is_shutting_down has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
2 | Member is_initialized has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
3 | Member sockaddr_inited has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
Incompatibility | Effect | |
1 | Size of this type has been changed from 17552 to 17560 bytes. | Change of type size may lead to different effects in different contexts. [+] ... |
Incompatibility | Effect | |
1 | Member limit_maxbytes has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
2 | Member bytes has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
3 | Member cmd_get has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
4 | Member threads has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
5 | Member bytes_read has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
6 | Member pointer_size has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
7 | Member total_items has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
8 | Member root has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
9 | Member curr_items has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
10 | Member rusage_system_seconds has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
11 | Member bytes_written has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
12 | Member evictions has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
13 | Member total_connections has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
14 | Member version has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
15 | Member pid has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
16 | Member rusage_user_seconds has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
17 | Member rusage_user_microseconds has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
18 | Member get_misses has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
19 | Member cmd_set has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
20 | Member uptime has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
21 | Member curr_connections has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
22 | Member time has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
23 | Member rusage_system_microseconds has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
24 | Member get_hits has been withdrawn from this type. | Applications will access incorrect memory when attempting to access this member. |
Incompatibility | Effect | |
1 | 2nd middle parameter port has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
Incompatibility | Effect | |
1 | 2nd middle parameter flag has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
Incompatibility | Effect | |
1 | 2nd middle parameter flag has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
Incompatibility | Effect | |
1 | 2nd middle parameter initial has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
Incompatibility | Effect | |
1 | 2nd middle parameter block has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
Incompatibility | Effect | |
1 | 2nd middle parameter value has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
Incompatibility | Effect | |
1 | 2nd middle parameter username has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
Incompatibility | Effect | |
1 | 2nd middle parameter hostname has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
Incompatibility | Effect | |
1 | 2nd middle parameter hostname has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
Incompatibility | Effect | |
1 | 3rd middle parameter port has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
2 | 2nd middle parameter hostname has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
Incompatibility | Effect | |
1 | 2nd middle parameter filename has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
Incompatibility | Effect | |
1 | 3rd middle parameter port has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
2 | 2nd middle parameter hostname has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
Incompatibility | Effect | |
1 | 3rd middle parameter key_length has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
2 | 2nd middle parameter key has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
Incompatibility | Effect | |
1 | 3rd middle parameter context has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
2 | 2nd middle parameter callback has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
Incompatibility | Effect | |
1 | 3rd middle parameter port has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
2 | 2nd middle parameter hostname has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
Incompatibility | Effect | |
1 | 3rd middle parameter port has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
2 | 4th middle parameter weight has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
3 | 2nd middle parameter hostname has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
Incompatibility | Effect | |
1 | 2nd middle parameter args has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
Incompatibility | Effect | |
1 | 3rd middle parameter func has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
2 | 2nd middle parameter args has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
Incompatibility | Effect | |
1 | 2nd middle parameter memc_stat has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
Incompatibility | Effect | |
1 | 3rd middle parameter key has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
2 | 2nd middle parameter memc_stat has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
Incompatibility | Effect | |
1 | 3rd middle parameter hostname has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
2 | 2nd middle parameter args has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
Incompatibility | Effect | |
1 | 6th middle parameter expiration has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
2 | 3rd middle parameter key_length has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
3 | 4th middle parameter value has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
4 | 5th middle parameter value_length has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
5 | 2nd middle parameter key has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
Incompatibility | Effect | |
1 | 8th middle parameter expiration has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
2 | 6th middle parameter value has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
3 | 3rd middle parameter master_key_length has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
4 | 7th middle parameter value_length has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
5 | 4th middle parameter key has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
6 | 5th middle parameter key_length has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
7 | 2nd middle parameter master_key has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
Incompatibility | Effect | |
1 | 6th middle parameter expiration has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
2 | 3rd middle parameter key_length has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
3 | 4th middle parameter value has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
4 | 5th middle parameter value_length has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
5 | 2nd middle parameter key has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
Incompatibility | Effect | |
1 | 8th middle parameter expiration has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
2 | 6th middle parameter value has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
3 | 3rd middle parameter master_key_length has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
4 | 7th middle parameter value_length has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
5 | 4th middle parameter key has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
6 | 5th middle parameter key_length has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
7 | 2nd middle parameter master_key has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
Incompatibility | Effect | |
1 | 6th middle parameter expiration has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
2 | 3rd middle parameter key_length has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
3 | 7th middle parameter flags has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
4 | 4th middle parameter value has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
5 | 5th middle parameter value_length has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
6 | 2nd middle parameter key has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
Incompatibility | Effect | |
1 | 8th middle parameter expiration has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
2 | 9th middle parameter flags has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
3 | 3rd middle parameter master_key_length has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
4 | 6th middle parameter value has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
5 | 4th middle parameter key has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
6 | 7th middle parameter value_length has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
7 | 2nd middle parameter master_key has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
8 | 5th middle parameter key_length has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
Incompatibility | Effect | |
1 | 6th middle parameter expiration has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
2 | 3rd middle parameter key_length has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
3 | 4th middle parameter value has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
4 | 5th middle parameter value_length has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
5 | 2nd middle parameter key has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
Incompatibility | Effect | |
1 | 8th middle parameter expiration has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
2 | 6th middle parameter value has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
3 | 3rd middle parameter master_key_length has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
4 | 7th middle parameter value_length has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
5 | 4th middle parameter key has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
6 | 5th middle parameter key_length has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
7 | 2nd middle parameter master_key has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
Incompatibility | Effect | |
1 | 6th middle parameter expiration has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
2 | 3rd middle parameter key_length has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
3 | 4th middle parameter value has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
4 | 5th middle parameter value_length has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
5 | 2nd middle parameter key has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
Incompatibility | Effect | |
1 | 8th middle parameter expiration has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
2 | 6th middle parameter value has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
3 | 3rd middle parameter master_key_length has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
4 | 7th middle parameter value_length has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
5 | 4th middle parameter key has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
6 | 5th middle parameter key_length has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
7 | 2nd middle parameter master_key has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
Incompatibility | Effect | |
1 | 6th middle parameter expiration has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
2 | 3rd middle parameter key_length has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
3 | 4th middle parameter value has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
4 | 5th middle parameter value_length has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
5 | 2nd middle parameter key has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
Incompatibility | Effect | |
1 | 8th middle parameter expiration has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
2 | 6th middle parameter value has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
3 | 3rd middle parameter master_key_length has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
4 | 7th middle parameter value_length has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
5 | 4th middle parameter key has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
6 | 5th middle parameter key_length has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
7 | 2nd middle parameter master_key has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
Incompatibility | Effect | |
1 | 3rd middle parameter minor_version has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |
2 | 2nd middle parameter major_version has been withdrawn from the interface signature. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack can be incorrectly initialized by applications. |