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

20050507: nex2gini seg faults in Solaris 9/10

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 20050507: nex2gini seg faults in Solaris 9/10
  • Date: Mon, 09 May 2005 12:30:23 -0600
Robert,

Can you provide any gdb output from a core file? I need something since
I can't duplicate any problem here.

I run here under X86 5.9 with WS10 compilers with no trouble. I did verify 
that WS10 again must not use the -O flag for the f77 compiler, so make sure 
you don't have that option set for your build. Is the crash duplicatable when 
processing the same SITE when you set the RADTIM time to a fixed time instead 
of current? If so, could be a zlib problem when reading the compressed 
product....
especially if you have a site where the file has been appended. That is, I
mean that the same station ID/time appears in the runtime list when the crash 
occurs.

Steve Chiswell
Unidata User Support





>From: Robert Mullenax <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200505071725.j47HPWP3016079

>The Unidata binary of GEMPAK 5.8.1 of nex2gini seg faults about 95% of the
>time whne running under Solaris 9 and Solaris 10 x86.  A few times it will
>work, the rest of the time it seg faults without producing a core file.
>
>I have also tried compiling locally and that does not help.  Setting system
>statcksize larger does not help and neither does reducing kxky.
>
>Thanks,
>Robert Mullenax
>
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publicly available
through the web.  If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.