[prev in list] [next in list] [prev in thread] [next in thread]
List: ggi-develop
Subject: Re: xcol palette problems
From: Christoph_Egger () t-online ! de (Christoph Egger)
Date: 2002-04-26 16:06:49
[Download RAW message or body]
On 24 Apr 2002, Gerard Braad wrote:
> > Set the env variable GGI_DEBUG=255 and send me the output, please.
> > This helps me to track down the problem better.
> >
>
> (run as root, with debug)
>
> Trying mode F1.[]
> Suggested mode 640x480.V640x480.F1.D1x1.[C16/16]
> Segmentation fault
>
>
> ldd dump:
> libggi.so.2 => /usr/local/lib/libggi.so.2 (0x40017000)
> libgii.so.0 => /usr/local/lib/libgii.so.0 (0x40022000)
> libgg.so.0 => /usr/local/lib/libgg.so.0 (0x40029000)
> libdl.so.2 => /lib/libdl.so.2 (0x4004d000)
> libc.so.6 => /lib/libc.so.6 (0x40051000)
> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
The usual output. That says nothing about why it crashs.
> gdb dump:
> Starting program: /home/g_braad/files/devel/ggi/libggi/libggi-2.0.1/programs/demos/.libs/demo
> Trying mode F1.[]
> Suggested mode 640x480.V640x480.F1.D1x1.[C16/16]
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x40031991 in GGI_X_flush (vis=0x804e900, x=0, y=0, w=640, h=480, tryflag=1)
> at mode.c:156
> 156 xcol.red = vis->palette[x].r;
Ah - you use the X-target, because of the GGI_X_flush().
Which value has x here?
Which values has priv->xwin.cmap_first and priv->xwin.cmap_last here?
> > Have you tried latest CVS sources? There are some more bugfixes.
>
> tried those too... same problem...
ok.
Please set the environment variable "export GGI_DEBUG=255" and send me the
output. This helps me to track down the problem better.
CU,
Christoph Egger
E-Mail: Christoph_Egger@t-online.de
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic