You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In most cases, a failure path would not have the consumer reading the debug list, but a separate bug documented in #10915 shows how this is still not right at present, and it does lead to crashes in those scenarios due to running off the end of the list.
The text was updated successfully, but these errors were encountered:
mcdurdin
changed the title
bug(core): debug lists may not be properly terminated for unhandled keys in kmx processor
bug(core): debug lists may not be properly terminated for failure paths in kmx processor
Mar 7, 2024
Coming out of #10919.
For example, the debug list is not terminated in this situation:
keyman/core/src/kmx/kmx_processevent.cpp
Lines 107 to 111 in 763bc96
The debug list is initialized immediately above:
keyman/core/src/kmx/kmx_processevent.cpp
Lines 92 to 98 in 763bc96
In most cases, a failure path would not have the consumer reading the debug list, but a separate bug documented in #10915 shows how this is still not right at present, and it does lead to crashes in those scenarios due to running off the end of the list.
The text was updated successfully, but these errors were encountered: