Bug 742307

Summary: Segmentation fault
Product: [Fedora] Fedora Reporter: Mateus Teixeira <mateus.teixeira>
Component: nclAssignee: Orion Poplawski <orion>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 14CC: orion
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: ncl-6.0.0-2.fc14 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-09 06:53:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Mateus Teixeira 2011-09-29 16:14:02 UTC
Description of problem:

When using ut_calendar function of NCL, the application is aborted and a segmentation fault is issued.


Version-Release number of selected component (if applicable): 5.2.1


How reproducible: always


Steps to Reproduce:
1. enter NCL, typing in a terminal

   ncl

2. create a small batch of data with an units attribute:

    x = (/1,2,3/)
    x@units = "days since 2000-1-1 00:00:00.0"

3. print the result of ut_calendar function:

    print( ut_calendar( x, -3 ) )

  
Actual results: NCL will be aborted and a segmentation fault is issued.

Expected results: the function used in step (3) sould return 

Variable: unnamed (return)
Type: integer
Total Size: 12 bytes
            3 values
Number of Dimensions: 1
Dimensions and sizes:	[3]
Coordinates: 
Number Of Attributes: 1
  calendar :	standard
(0)	2000010200
(1)	2000010300
(2)	2000010400

Additional info: none

Comment 1 Orion Poplawski 2011-09-29 17:20:16 UTC
As workaround try setting the UDUNITS_PATH environment variable to /usr/share/udunits.

Comment 2 Orion Poplawski 2011-09-29 20:48:43 UTC
What is your thought on updating ncl to 6.0.0 in F14?  I'm leaning towards doing so if only because this issue having existed so long without anyone reporting it leads me to believe that almost no one is using these binaries.

Comment 3 Mateus Teixeira 2011-09-29 23:55:20 UTC
I was using these binaries because it has been more easy to teach my students to use NCL without worry about installation details from NCL's official website. After noted this issue, I was planning to erase them from all computers. However, if a update that fix this issue is available, I'll continue to use them on future installations.

Comment 4 Fedora Update System 2011-09-30 16:14:13 UTC
ncl-6.0.0-2.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/ncl-6.0.0-2.fc14

Comment 5 Fedora Update System 2011-09-30 16:14:21 UTC
ncl-6.0.0-2.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/ncl-6.0.0-2.fc15

Comment 6 Fedora Update System 2011-10-01 01:53:31 UTC
Package ncl-6.0.0-2.fc14:
* should fix your issue,
* was pushed to the Fedora 14 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing ncl-6.0.0-2.fc14'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/ncl-6.0.0-2.fc14
then log in and leave karma (feedback).

Comment 7 Mateus Teixeira 2011-10-05 17:45:23 UTC
It's working very nicely!

In addition, the location of libraries is the official one. In 5.2.1 version, they were installed in $NCARG_ROOT/share/ncarg/nclscripts/csm. Now, they are in $NCARG_ROOT/lib/...

Comment 8 Mateus Teixeira 2011-10-05 17:48:27 UTC
Please, as this update is available, inform people of ncl-talk about it. It's a very easy way to install NCL in fedora system.

Comment 9 Fedora Update System 2011-10-09 06:53:09 UTC
ncl-6.0.0-2.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 10 Fedora Update System 2011-10-09 06:57:52 UTC
ncl-6.0.0-2.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.