nanogui: Segfault in fblin32.c, line 77


Previous by date: 22 Apr 2008 20:53:04 -0000 Re: Segfault in fblin32.c, line 77, Greg Haerr
Next by date: 22 Apr 2008 20:53:04 -0000 Re: Segfault in fblin32.c, line 77, Pascal Tritten, Railtec Systems GmbH
Previous in thread: 22 Apr 2008 20:53:04 -0000 Re: Segfault in fblin32.c, line 77, Greg Haerr
Next in thread: 22 Apr 2008 20:53:04 -0000 Re: Segfault in fblin32.c, line 77, Pascal Tritten, Railtec Systems GmbH

Subject: Re: [nanogui] Segfault in fblin32.c, line 77
From: "Greg Haerr" ####@####.####
Date: 22 Apr 2008 20:53:04 -0000
Message-Id: <01e301c8a4ba$dc78dd80$0300a8c0@RDP>

: #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

Previous by date: 22 Apr 2008 20:53:04 -0000 Re: Segfault in fblin32.c, line 77, Greg Haerr
Next by date: 22 Apr 2008 20:53:04 -0000 Re: Segfault in fblin32.c, line 77, Pascal Tritten, Railtec Systems GmbH
Previous in thread: 22 Apr 2008 20:53:04 -0000 Re: Segfault in fblin32.c, line 77, Greg Haerr
Next in thread: 22 Apr 2008 20:53:04 -0000 Re: Segfault in fblin32.c, line 77, Pascal Tritten, Railtec Systems GmbH


Powered by ezmlm-browse 0.20.