From: Peter Amstutz <amstpi@freenet.tlh.fl.us>
  To  : ggi-develop@eskimo.com
  Date: Sun, 23 Aug 1998 13:35:08 -0400 (EDT)

Re: debugging libggi...

On Sun, 23 Aug 1998, Marcus Sundberg wrote:

> Andrew Apted wrote:
> > 
> > Peter Amstutz writes:
> > 
> > >  Right now the X target seems broken (I'm working against anon cvsdevel
> > >  from a few hours ago)
> > 
> > Mine doesn't even compile here.  The offending lines are in
> > display/X/visual.c :
> > 
> >     int first = vis->app_dbs.first_targetbuf;
> >     int last = vis->app_dbs.last_targetbuf;
> 
> Ouch, I thought I tested that code. :-(
> It's fixed now anyway.
> 
> > Marcus, what are these for ?
> 
> If we want extensions to be able to handle DirectBuffers the
> target needs to know which buffers that belongs to it.
> The idea is that extensions that mess with the DB lists update
> these entries accordingly, so the target can now which buffers
> to free.

That reminds me.  vis->app_dbs->last_targetbuf should be set to -1
initially, otherwise when opening a visual it will attempt to free()
directbuffer[0]...  Bad thing.  Causes segfaults ya know.  Is that fixed?

Let's see, the GLIDE target doesn't compile either, and I think
one of the files in display-sub is causing gcc 2.8.1 to catch signal 11!
Ugh.  Libggi still needs some work, guys.

Peter Amstutz

/* 
E-mail:
	amstpi@freenet.tlh.fl.us
Home Page:
	http://www.freenet.tlh.fl.us/~amstpi/
Geek Code: (see http://www.geekcode.com/ for decoding instructions)
  GCS d- s:+ a--- C++>$ UL++++>$ P+(++) L++>$ E W++ N+ !o K w-- !O M-() !V
  PS+(++) PE-(--) Y+ PGP t 5++ X+ R tv b+ DI+ D++ G e h 
*/