Bug 2179857 - reading file causes crash on s390x
Summary: reading file causes crash on s390x
Keywords:
Status: POST
Alias: None
Product: Fedora
Classification: Fedora
Component: netcdf
Version: 42
Hardware: s390x
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Orion Poplawski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1998838 2173469
TreeView+ depends on / blocked
 
Reported: 2023-03-20 10:00 UTC by david08741
Modified: 2025-02-26 12:53 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)
Problematic netcdf file (42.52 KB, application/x-hdf)
2023-03-20 10:01 UTC, david08741
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github Unidata netcdf-c issues 2670 0 None open ncdump fails on s390x 2023-03-22 01:04:46 UTC

Description david08741 2023-03-20 10:00:36 UTC
Description of problem:
Reading attached fail fails on s390x

Version-Release number of selected component (if applicable):
netcdf-4.8.1-3.fc36.s390x

How reproducible:
always

Steps to Reproduce:
1. ncdump -h somefile.nc

Actual results:
[...]
	double tt ;
	double ZMAX ;
	double ZMIN ;
	double BOUT_VERSION ;
NetCDF: Invalid dimension ID or name
Location: file ../../ncdump/ncdump.c; line 1750
	double dx(x, 

Expected results:
same as on other arches

Additional info:

Comment 1 david08741 2023-03-20 10:01:17 UTC
Created attachment 1951983 [details]
Problematic netcdf file

Comment 2 Orion Poplawski 2023-03-22 01:04:46 UTC
I'm assuming this is your upstream bug report?  Linking it here as they are the best hope in getting this resolved.

Comment 3 Ben Cotton 2023-04-25 18:26:58 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 4 Fedora Release Engineering 2023-08-16 07:12:00 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.

Comment 5 Aoife Moloney 2024-11-08 10:50:00 UTC
This message is a reminder that Fedora Linux 39 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '39'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 39 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 6 Aoife Moloney 2025-02-26 12:53:28 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle.
Changing version to 42.


Note You need to log in before you can comment on or make changes to this bug.