Re: bug in 21.5-b31 crash in redisplay.c similar to issue 697-further clue

One further piece of information: The mouse is somehow involved in the problem. I can load the bottom menu, click the bottom open button, and the find-file dialog comes up. If my hand is off the mouse at that point, everything looks as it should. I can type commands and the commands go in the mini-buffer as expected. And I can move the mouse cursor as long as it is off the XEmacs window. As soon as I move the mouse cursor on to the XEmacs window (anywhere), XEmacs crashes and goes away. Yes, but the first time I omitted the rest of the buttons duplicating the default menu at the top for clarity. Testing after omitting, still showed the bug was acting the same way, so I sent a simplified version first. Steve Mitchell On 07/07/2011 11:29 PM, Stephen J. Turnbull wrote: > steven Mitchell writes: > > > If I use the open button on the default toolbar, it works fine. > > I also noticed the bottom toolbar shows up on the find-file dialog > > before it crashes. > > > It is similar to issue 697, but triggered differently. Should I start > > another issue? Or put this in as a message under that issue? > > Thanks for the report. I think you should add it to issue697, with a > comment that it is triggered differently. The underlying mechanism > seems to be the same, however, see below. > > > > Fatal error: assertion failed, file redisplay.c, line 9179, pos>= 0&& > > pos< dy->largest_ > > #0 0x00007faa25105035 in raise () from /lib64/libc.so.6 > > #1 0x00007faa251069e6 in abort () from /lib64/libc.so.6 > > #2 0x00000000004ab495 in really_abort () at emacs.c:4792 > > #3 0x00000000004aa010 in assert_failed (file=0x6d22e0 "redisplay.c", > > line=9179, expr=0x6b9958 "pos>= 0&& pos< dy->largest_") at emacs.c:4089 > > #4 0x00000000004d8e91 in Dynarr_verify_pos_atp (d=0x1237920, pos=-1, > > file=0x6d22e0 "redisplay.c", line=9179) at array.h:202 > > I was going to ask you to get more information, but I think it's right > there: "pos=-1". The Dynarr has not been initialized (it has > allocated no storage for content, only the storage management struct > is present). I don't know why this happens, but I've seen it in other > line 9179 crashes. > > Cool! Well, not, but you know what I mean. > > _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta