From: =?iso-8859-1?Q?Niklas_H=F6glund?= <niklas@canit.se>
  To  : ggi-develop@eskimo.com
  Date: Wed, 23 Jun 1999 18:07:44 +0200

Re: ggi acting up?

On Tue, Jun 22, 1999 at 01:19:25AM +0200, Ketil Froyn wrote:
> #0  0x4011b5a8 in main_arena ()
> #1  0x4007bf06 in buffered_vfprintf (s=0x4011b500, format=0x4002049e "%s:
> ", 
>     args=0xbffed598) at vfprintf.c:1752
> #2  0x40077856 in _IO_vfprintf (s=0x4011b500, format=0x4002049e "%s: ", 
>     ap=0xbffed598) at vfprintf.c:1018
> #3  0x4007f6f7 in fprintf (stream=0x4011b500, format=0x4002049e "%s: ")
>     at fprintf.c:32
> #4  0x4001f985 in ggDPrintf (sync=0, subsys=0x4003184a "LibGII", 
>     form=0x4003183c "Debugging=%d\n") at debug.c:38
> #5  0x4002fa7e in giiInit () at init.c:115
> #6  0x40017670 in ggiInit () at init.c:69
> #7  0x80493b3 in main (argc=0, argv=0xbffffb54) at demo.c:293
> #8  0x4004acb3 in __libc_start_main (main=0x80491e8 <main>, argc=1, 
>     argv=0xbffffb54, init=0x8048c18 <_init>, fini=0x804a92c <_fini>, 
>     rtld_fini=0x4000a350 <_dl_fini>, stack_end=0xbffffb4c)
>     at ../sysdeps/generic/libc-start.c:78

I recognise this. I don't know for sure what I did to solve it, but it
might have been upgrading glibc or egcs.

-- 
						Niklas