Complete.Org: Mailing Lists: Archives: freeciv-dev: December 2002:
[Freeciv-Dev] Re: (PR#2534) civclient crash on FreeBSD 5.0
Home

[Freeciv-Dev] Re: (PR#2534) civclient crash on FreeBSD 5.0

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: mwlucas@xxxxxxxxxxxxxxxxxxxx
Subject: [Freeciv-Dev] Re: (PR#2534) civclient crash on FreeBSD 5.0
From: "Jason Short via RT" <rt@xxxxxxxxxxxxxx>
Date: Fri, 13 Dec 2002 03:03:17 -0800
Reply-to: rt@xxxxxxxxxxxxxx

On Fri, 2002-12-13 at 04:40, Raimar Falke via RT wrote:
> On Thu, Dec 12, 2002 at 05:50:57PM -0800, Jason Short via RT wrote:
> > On Thu, 2002-12-12 at 17:16, mwlucas@xxxxxxxxxxxxxxxxxxxx via RT wrote:
> > > BTW, I tried the beta of 1.14.0.  Same behaviour.
> > > 
> > > Thanks for all your help!
> > 
> > Try this patch.
> > 
> > Question: what machine (chipset) are you running on?
> > 
> > Raimar: see http://www.eskimo.com/~scs/C-faq/q5.2.html.  It may, but
> 
> This only matters if sizeof(void *)!=sizeof(int) or (int)NULL != 0. I
> doubt that you can find a system where the second is true.

Err, yes.  Hence the question.  Although I suspect it might also be
possible if the compiler doesn't like you.

But it appears that this is not the problem in this case (I jumped to
that conclusion when I saw the "new" crash was caused by one of the
cases I had not fixed).

BTW: you can have GTK automatically set the pointer to NULL when the
dialog goes away.  Something like

  gtk_signal_connect(GTK_OBJECT(parent),
                     "destroy",
                     GTK_SIGNAL_FUNC(gtk_widget_destroyed),
                     &parent);

And another note: it is likely this bug is also in the GTK2 client. 
Michael, can you test this?

jason




[Prev in Thread] Current Thread [Next in Thread]