>> > For instance, Eli recently added this code (dispnew.c): >> > >> > /* This should never happen, but evidently sometimes does if one >> > resizes the frame quickly enough. Prevent aborts in cmcheckmagic. */ >> > if (vpos >= FRAME_TOTAL_LINES (f)) >> > return; >> > >> > But this is checking the *frame*. Later, the assertion in >> > cmcheckmagic will be made about the *terminal*. >> >> Right. This should probably be >> >> if (FRAME_TERMCAP_P (f) && vpos >= FrameRows (FRAME_TTY (f))) >> return; > > That code is in update_frame_line, which is used only for TTY frames > and uses frame glyph matrices. IOW, it updates the entire frame as a > single large window. In addition, on a TTY terminal there's only one > frame visible at any given time, and only that one frame is being > redrawn, ever. > > Given the above, why is that code incorrect?
It _might_ be incorrect when we allow FRAME_TOTAL_LINES (f) to exceed FrameRows (FRAME_TTY (f)) because we refuse to shrink a frame below some height. That's why I used the term "probably". If I knew what that code does in all consequences, I could tell you more. But I don't know. >> And it's not about resizing frames "quickly". Here I can crash it in a >> very slow fashion too. > > Good for you, but my comment describes the situation in which I saw > that particular problem. As I already said, I can never crash Emacs > if I resize the terminal emulator window slowly. And as I already said I can crash Emacs reliably if I slowly shrink the window, slowly expand it again, precisely at the moment it should reshow the minibuffer window. You can ask me any question about the state of the frame and its windows at the time of the crash. > Most probably because the terminal driver simply ignores such writes. > AFAIU, the assertion there is not because of the terminal, it is there > to catch Emacs bugs. Then tell us how to catch it. I'm already out of ideas. martin
