: #0 0x0000000000425ae5 in linear32_drawhorzline (psd=0x6df4c0, x1=511, : x2=639, y=240, c=0) at src/drivers/fblin32.c:77 : #1 0x000000000041834a in gen_fillrect (psd=0x6df4c0, x1=0, y1=241, : x2=639, y2=479, c=0) at src/drivers/genmem.c:80 : #2 0x000000000041a25f in X11_fillrect (psd=0x6cc920, x1=0, y1=0, : x2=639, y2=479, c=0) at src/drivers/scr_x11.c:979
Oops I just noticed that you're running nano-X on X11, not FB. The X11 driver keeps "savebits" by commanding X11, then drawing using the fb32 driver. It looks like perhaps the size malloced could be incorrect. This is calced in the genmem.c file, I think, but you'll need to look hard at the X11 driver to trace where it alloced the savebits fb buffer in the first place. I'm not aware of any X11 driver problems, so its a bit strange... Regards, Greg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
