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

[netCDF #JJD-454907]: nctest segfault

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: [netCDF #JJD-454907]: nctest segfault
  • Date: Thu, 30 Jun 2016 11:18:05 -0600
Hi,

Can you provide the config.log and test-suite.log files generated when you ran 
configure and make check?  That should provide additional information I can use 
to try to replicate this issue.

Thanks, have a great afternoon,

-Ward

> Hello,
> 
> I just built NetCDF 4.4.1 on a Linux workstation,
> and `make check` gives this output:
> 
> make[3]: Entering directory '/home/dibanez/build/netcdf-4.4.1/nctest'
> /home/dibanez/src/netcdf-4.4.1/test-driver: line 107:  2341 Segmentation
> fault      (core dumped) "$@" > $log_file 2>&1
> FAIL: nctest
> PASS: tst_rename
> FAIL: compare_test_files.sh
> ============================================================================
> Testsuite summary for netCDF 4.4.1
> ============================================================================
> # TOTAL: 3
> # PASS:  1
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  2
> # XPASS: 0
> # ERROR: 0
> ============================================================================
> See nctest/test-suite.log
> Please report to address@hidden
> ============================================================================
> Makefile:786: recipe for target 'test-suite.log' failed
> 
> 


Ticket Details
===================
Ticket ID: JJD-454907
Department: Support netCDF
Priority: Normal
Status: Closed
===================
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.