From: becka@rz.uni-duesseldorf.de
  To  : ggi-develop@eskimo.com
  Date: Mon, 15 Feb 1999 16:28:09 +0100 (MET)

Re: "terminating on signal 11" problem, 2nd try

Hi !

> i just tried to set the correct default mode, but it doesn't
> make any difference. so i turned on the debug mode as suggested
> and here are the results.

O.K. - I'll habe a look.

> btw: the "configure" on the latest developer snapshots is always
> 0 bytes.. do i really need to "autoconf" myself? 

What ??? That's a bug and should be fixed.

> Trying mode F1.[]

That looks strange, but ...

> LibGG: mode.c:149: ggiCheckMode(0x804de38, 0xbffeea38) called
> LibGG: mode.c:521: display-fbdev: checkmode 800x600#0x0F1[0x4000808]
> LibGG: mode.c:622: display-fbdev: result 0 800x600#800x600F1[0x4000808]
> Suggested mode 800x600.V800x600.F1.D1x1.[P8/8]

O.K. - that looks good.

> LibGG: mode.c:252: display-fbdev: frame_size=0x75300 fb_size=0x75300
> mmap_size=0x76000

Hmm - looks o.k. as well.

> LibGG: mode.c:257: display-fbdev: FB_PTR=0x400ee000

That as well looks like the mmap went o.k.

> LibGG: mode.c:130: ggiSetMode: fillscreen
> Terminating on signal 11

Very strange in deed. It looks like there is a problem with mmaping the
graphics memory, andf it then segfaults when accessing it. I'll need the 
strace logs as well for that one. At best make a "mixed" log by :

GGI_DEBUG=255 strace ./demo

It might also help, if I get a gdb backtrace and/or the exact line in which
the segfault occurs. But disregard that, if you aren't proficient with gdb.

What fbcon driver are you using BTW ?

CU, ANdy

-- 
= Andreas Beck                    |  Email :  <andreas.beck@ggi-project.org> =