Description of problem: ncdump segfaults when run without any arguments. Version-Release number of selected component (if applicable): netcdf-3.6.1-4.fc6 How reproducible: Always. Steps to Reproduce: 1. ncdump Actual results: Segmentation fault (core dumped) Expected results: It complains one has to give it a file to dump. Additional info: Backtrace: Running: gdb /usr/bin/ncdump ./core.17342 Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `ncdump'. Program terminated with signal 11, Segmentation fault. #0 0x0000003265a74e00 in strchr () from /lib64/libc.so.6 #0 0x0000003265a74e00 in strchr () from /lib64/libc.so.6 #1 0x0000003265a758fe in strrchr () from /lib64/libc.so.6 #2 0x00000000004030f0 in main (argc=0, argv=0x7fff03f66468) at ncdump.c:88 #3 0x0000003265a1da44 in __libc_start_main () from /lib64/libc.so.6 #4 0x00000000004013b9 in _start () It probably tries to parse NULL or something like that...
Hi David, I'm able to reproduce this bug on i386 as well. And it doesn't appear to be specific to the Fedora netcdf package. So I've reported it to the upstream folks: http://www.unidata.ucar.edu/software/netcdf/ http://www.unidata.ucar.edu/support/help/MailArchives/netcdfgroup-list/maillist.html and hopefully it'll be fixed in a future release.
Upstream reports that this issue is fixed in 3.6.2beta. And I'll update the Fedora package soon after the upstream 3.6.2 final release.