[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[GEMPAK #XBI-500547]: FW: Segmentation Fault after second modify source with world proj ection of grib in nmap2

Stephen,

I have not been able to duplicate this problem here under Fedora 3 32 bit or 
Fedora 4 64 bit.
The 2.4 kernel is much older than I have here, and the gcc environment you have 
also
has an older glibc than I have. I might suggest using the "-g" flag in 
$CONFIGDIR/Makeinc.linux FOPT and COPT when building to see what routine the 
segmentation fault is occuring
in if you run under gdb.

I can post a 5.9.2 in progress distribution if you want to test that.

Steve Chiswell
Unidata User Support



> I noticed that this will happen with both the binary and source install of
> GEMPAK5.9.1, when using nmap2 as described below.
> 
> However it appears to only on the one system:
> 
> Linux gempak3.testdev.pelmorex.com 2.4.9-e.25 #1 Fri Jun 6 18:27:21 EDT 2003
> i686 i686 i386 GNU/Linux
> 
> On closer scrutiny, I noticed the following difference in the make.out from
> source installations on other machines...
> 
> checking if gcc supports -fno-rtti -fno-exceptions... no
> 
> Does anyone know what might be difficient?
> 
> The compilier?
> 
> gcc -v
> Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.3.3/specs
> Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
> --infodir=/usr/share/info --enable-shared --enable-threads=posix
> --disable-checking --disable-libunwind-exceptions --with-system-zlib
> --enable-__cxa_atexit --host=i386-redhat-linux
> Thread model: posix
> gcc version 3.3.3 20040412 (Red Hat Linux 3.3.3-7)
> 
> Stephen Sinnis
> Pelmorex Media Inc
> Tel: (905) 829-1159 (1379)
> Fax: (905) 829-5800
> 
> 


Ticket Details
===================
Ticket ID: XBI-500547
Department: Support GEMPAK
Priority: Critical
Status: Closed