2025/10/31 18:13、[email protected]のメール:

(3) Editing an exponent in a math inset.  Crash was more severe (I got a message that a SIGSEGV error was caught and LyX (including the message box) were unresponsive. So I had to force quit Risk.  A crash report was not generated. Time Machine was not backing up files. LyX created an emergency file.

This is probably because GuiInputMehod::initializePositions() that defines d->cur_row_idx_ makes +1 adjustment when the real cursor is on boundary. It causes memory allocation error when d->cur_row_idx_ is mistakenly used as an index of a vector. This error can occur only when the real cursor is on boundary at the end of d->rows_ and the input method is on.

In the attached fix, I put out the boundary adjustment from GuiInputMehod::initializePositions() and make same adjustment at places it is used. Probably this would be better than keeping the definition of the above function for the definition of d->cur_row_idx_ to be less confusing.

I’m going to post the fix to the source after some tests.

Koji

Attachment: boudary_fix.patch
Description: Binary data

-- 
lyx-devel mailing list
[email protected]
https://lists.lyx.org/mailman/listinfo/lyx-devel

Reply via email to