Lines Matching full:may
18 …l of any virtual method at higher position in this class or its subclasses may result in crash or …
40 …l of any virtual method at higher position in this class or its subclasses may result in crash or …
58 …ontain a pointer to added virtual method. Call of any method in this class may result in crash or …
114 …d or any virtual method at higher position in this class or its subclasses may result in crash or …
132 …d or any virtual method at higher position in this class or its subclasses may result in crash or …
169 …ss parameters of older replaced method to newly added virtual method. This may result in crash or …
187 …ethod to the library instead of expected newely added virtual method. This may result in crash or …
205 Call of any method in this class may result in crash or incorrect behavior of applications.
223 …The layout of v-table has been changed. Call of this virtual method may result in crash or incorre…
241 …The layout of v-table has been changed. Call of this pure virtual method implementation may result…
314 …Previous accesses of applications to public fields of this class or its subclasses may be incorrec…
332 …allocate an older memory layout. Call of any exported method of this class may access a memory out…
369 Size, memory layout and v-table layout of this class and subclasses may change.
387 Size, memory layout and v-table layout of this class and subclasses may change.
629 …The fields or parameters of such data type may be incorrectly initialized or accessed by old clien…
647 …The fields or parameters of such data type may be incorrectly initialized or accessed by old clien…
665 …has been changed and therefore parameters at higher positions in the stack may be incorrectly init…
739 …NOTE: this field should be accessed only from the new library functions, otherwise it may result i…
759 …NOTE: this field should be accessed only from the new library functions, otherwise it may result i…
777 …anged and therefore fields at higher positions of the structure definition may be incorrectly acce…
796 …anged and therefore fields at higher positions of the structure definition may be incorrectly acce…
815 …NOTE: this field should be accessed only from the new library functions, otherwise it may result i…
833 …anged and therefore fields at higher positions of the structure definition may be incorrectly acce…
852 …anged and therefore fields at higher positions of the structure definition may be incorrectly acce…
871 …NOTE: this field should be accessed only from the new library functions, otherwise it may result i…
889 …NOTE: this field should be accessed only from the new library functions, otherwise it may result i…
926 …anged and therefore fields at higher positions of the structure definition may be incorrectly acce…
964 …anged and therefore fields at higher positions of the structure definition may be incorrectly acce…
1000 …anged and therefore fields at higher positions of the structure definition may be incorrectly acce…
1018 …anged and therefore fields at higher positions of the structure definition may be incorrectly acce…
1037 1) Applications may access incorrect memory when attempting to access this field.
1056 Applications may access incorrect memory when attempting to access this field.
1074 Renaming of a field in data type may indicate a change in the semantic meaning of the field.
1110 … Applications may execute a wrong branch of code in the library and therefore change the behavior.
1128 …This may result in crash or incorrect behavior of applications because the library may not handle …
1146 … Applications may execute a wrong branch of code in the library and therefore change the behavior.
1182 … Applications may execute a wrong branch of code in the library and therefore change the behavior.
1200 … Replacement of the field data type may indicate a change in the semantic meaning of the field.
1218 This field may be incorrectly initialized or accessed by applications.
1236 …y functions to this field and fields at higher positions of the structure definition may be broken.
1254 1) This field may be incorrectly initialized or accessed by applications.
1274 …y functions to this field and fields at higher positions of the structure definition may be broken.
1292 … and library functions to the fields at higher positions of the structure definition may be broken.
1347 … and library functions to the fields at higher positions of the structure definition may be broken.
1383 Replacement of field base type may indicate a change in the semantic meaning of the field.
1401 …The library functions may try to access unallocated memory by the dereferencing of old field value…
1419 …is field as the lower-dimension array and will not read all elements. This may change the behavior…
1437 Previous accesses of applications and library functions to this field may be broken.
1455 Previous accesses of applications and library functions to this field may be broken.
1473 …y functions to this field and fields at higher positions of the structure definition may be broken.
1492 2) Previous accesses of applications and library functions to this field may be broken.
1511 …y functions to this field and fields at higher positions of the structure definition may be broken.
1529 … and library functions to the fields at higher positions of the structure definition may be broken.
1584 … and library functions to the fields at higher positions of the structure definition may be broken.
1602 Replacement of the base data type may indicate a change in its semantic meaning.
1620 …The fields or parameters of such data type may be incorrectly initialized or accessed by old clien…
1662 …has been changed and therefore parameters at higher positions in the stack may be incorrectly init…
1680 …has been changed and therefore parameters at higher positions in the stack may be incorrectly init…
1698 …will pass an old default (compile-time) argument that may not be properly handled anymore. This ma…
1716 … default argument (that is not default any more) that may not be properly handled anymore. This ma…
1752 … value. Also, distribution of other parameters on the available registers and stack may be changed.
1770 …has been changed and therefore parameters at higher positions in the stack may be incorrectly init…
1788 …has been changed and therefore parameters at higher positions in the stack may be incorrectly init…
1806 …The parameter became passed in the register instead of the stack. This may result in crash or inco…
1824 …The parameter became passed through the stack instead of the register. This may result in crash or…
1842 Replacement of parameter data type may indicate a change in its semantic meaning.
1860 …This function may change parameter @target, but it will be treated as const by old client applicat…
1878 …This function may change parameter @target, but it will be treated as const by old client applicat…
1896 …r is modified, no other pointer will access that same memory. The compiler may choose to optimize …
1932 The parameter may be passed in a register instead of the calling stack.
1968 …Violation of the calling convention. This may result in crash or incorrect behavior of application…
1986 …Violation of the calling convention. This may result in crash or incorrect behavior of application…
2022 …Violation of the calling convention. This may result in crash or incorrect behavior of application…
2040 …The return value will be treated as non-const by old client applications. This may result in crash…
2058 …The return value will be treated as non-const by old client applications. This may result in crash…
2076 This parameter may be incorrectly initialized by applications.
2094 Replacement of parameter base type may indicate a change in its semantic meaning.
2112 …The library function may try to access unallocated memory by the dereferencing of old parameter va…
2130 …arameter as the lower-dimension array and will not read all elements. This may change the behavior…
2131 NOTE: if this is out-parameter then this change may cause a crash of applications.
2149 Applications will obtain a different return value and execution may change.
2167 Applications will obtain a different value and execution may change.
2185 Replacement of return type may indicate a change in its semantic meaning.
2203 Replacement of data type may indicate a change in semantic meaning.
2221 This global data may be incorrectly accessed by applications.
2239 Applications will obtain a different value and execution may change.
2257 Applications will not obtain a return value and execution may change.
2349 Replacement of return type may indicate a change in its semantic meaning.
2443 …compile time. Any attempts to change this global data by library functions may result in crash of …
2461 …applications. Any attempts to change this global data by library functions may result in undefined…
2479 Any attempts of old applications to change this global data may result in crash.
2497 Any attempts of old applications to change this global data may result in crash.
2515 Applications will obtain a different return value and execution may change.
2533 Replacement of return base type may indicate a change in its semantic meaning.
2551 …rn value as the lower-dimension array and will not read all elements. This may change the behavior…
2569 …Applications may try to access unallocated memory by the dereferencing of new return value and the…
2659 …has been changed and therefore parameters at higher positions in the stack may be incorrectly init…
2677 …has been changed and therefore parameters at higher positions in the stack may be incorrectly init…
2695 …has been changed and therefore parameters at higher positions in the stack may be incorrectly init…
2713 …has been changed and therefore parameters at higher positions in the stack may be incorrectly init…
2731 Renaming of a parameter may indicate a change in its semantic meaning.
2749 …ction on binary level has been changed from @old_value to @new_value. This may cause "undefined re…
2767 …ction on binary level has been changed from @old_value to @new_value. This may cause "undefined re…
2785 …ction on binary level has been changed from @old_value to @new_value. This may cause "undefined re…
2803 …ction on binary level has been changed from @old_value to @new_value. This may cause "undefined re…
2821 …ction on binary level has been changed from @old_value to @new_value. This may cause "undefined re…
2839 … data on binary level has been changed from @old_value to @new_value. This may cause "undefined re…
2857 …ction on binary level has been changed from @old_value to @new_value. This may cause "undefined re…
2875 …ction on binary level has been changed from @old_value to @new_value. This may cause "undefined re…
2893 …ction on binary level has been changed from @old_value to @new_value. This may cause "undefined re…
2911 …ction on binary level has been changed from @old_value to @new_value. This may cause "undefined re…
2929 …ction on binary level has been changed from @old_value to @new_value. This may cause "undefined re…
2947 …arameter to the new-version library functions, that expect a new one. This may result in crash of …
2983 … The value of this constant may no longer be properly handled by new-version library functions.
3037 …Old client applications will get volatile object instead of non-volatile, but may be optimized by …
3055 …Old client applications will pass volatile object to the function that may be optimized by the com…
3073 This field may be incorrectly initialized or accessed by applications.
3091 This field may be incorrectly initialized or accessed by applications.
3109 This parameter may be incorrectly initialized by applications.
3127 This parameter may be incorrectly initialized by applications.
3145 Applications will obtain a different return value and execution may change.
3163 …return value. Also, distribution of parameters on the available registers and stack may be changed.
3181 This parameter may be incorrectly initialized by applications.
3199 This parameter may not be initialized by old clients.
3217 The semantic meaning of the parameter may change.
3253 …Applications will use an old value of this data instead of the new one. This may cause incorrect b…
3307 …Old applications will continue using this method, but it may require a different initialization of…
3325 …Old applications will continue using this method, but it may require a different initialization of…
3361 …Old applications will continue using this global data, but it may require a different initializati…
3379 …Old applications will continue using this global data, but it may require a different initializati…
3487 …Old applications will continue using this field, but it may require a different initialization of …
3505 …Old applications will continue using this field, but it may require a different initialization of …
3523 …Old applications will not provide implementation for this pure virtual method. This may result in …
3559 …tructure of this type is hidden in the new library version and may be different. This may result i…