[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-gnubg] Another crash report....
From: |
Joern Thyssen |
Subject: |
Re: [Bug-gnubg] Another crash report.... |
Date: |
Mon, 16 Dec 2002 18:19:09 +0000 |
User-agent: |
Mutt/1.4i |
On Mon, Dec 16, 2002 at 05:33:21PM +0100, Øystein Johansen wrote
> >Ick. Now that I read more closely, it seems that the bug I found was not
> >the same as yours. The problem I found was caused by the board label
> >text not being entirely contained within the board (now fixed in CVS).
> >Hopefully that fixes your problem too...
>
> No. it didn't, but....
>
> > if not, one thing that might
> >cause problems with big boards is a small stack size limit. The
> >g_alloca() at the end of board_expose() could use a couple of megabytes of
> >stack space -- does replacing that with a malloc() (which can be free()d
> >immediately after the gdk_draw_rgb_image() call) help?
>
> ... this change did the trick!
>
Mine still crashes after opening dialogs with evalcontexts. Both
Settings->Chequer play and Settings->cube decision crashes.
The gtk_object_get_user_data in EvalOK returns a NULL pointer. I tried
with gtk_object_get_user_data right after the gtk_object_set_data_full
in EvalWidget, but I still get an NULL pointer.
Using gtk_object_get_data seems to do the trick, but I would really like
to know why it suddenly stopped working.
Jørn