[Xastir] Re: Crash on 64-bit FC3

[Derrick J Brashear]

On Thu, 7 Oct 2004, Jim King wrote:

> A little bit of looking at the source code was inspirational, and I think 
> I've found the problem.  It looks to me like the XtVaXXX functions require a 
> NULL as the final parameter to signal the end of argument list.  In main.c, a 
> little over half of the calls to XtVaGetValues use "0" as the final 
> parameter, and the rest of the calls use "NULL" as the final parameter.  I 
> think that all of the calls to other XtVaXXX functions use "NULL" as the 
> final parameter.  On x86_64, int's are still 32 bits, but pointers are 64 
> bits, so "0" (an int) and "NULL" (a pointer) are not the same thing.  I 
> changed all the of the 0 final parameters to NULL in calls to XtVaGetValues 
> and Xastir seems to run OK now.

Ok, fixed (and there's one in db.c) in CVS.