NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Hi, Cedric: The error was found and corrected, it was caused by the violation of the rule "If you try to read all the values of a record variable into an array but there are more records in the file than you assume, more data will be read than you expect, which may cause a segmentation violation." Thanks much. regards. Jinyun Ph.D Candidate. Depart of Earth & Atmospheric Sciences, Purdue university. http://web.ics.purdue.edu/~tang16 ________________________________________ From: Cedric Roux [cedric.roux@xxxxxxxxxx] Sent: Friday, February 05, 2010 4:02 AM To: Tang, Jinyun Cc: netcdfgroup@xxxxxxxxxxxxxxxx Subject: Re: [netcdfgroup] help with "ncx.c: No such file or directory" >> with the error "signal SIGSEGV, Segmentation fault. >> 0x0000000000444ecb in ncx_getn_float_float (xpp=0x7fff18c7b1d8, >> nelems=2048, >> tp=0x2ae8401ae010) at ncx.c:3475 >> 3475 ncx.c: No such file or directory." by the way, you are using gdb, right? So in your case, after the crash, gdb sees where the error comes from and tries to show you some source code. It looks for ncx.c but cannot find it.
netcdfgroup
archives: