> Ward & Russ - thanks for the response. By the way I rather not trouble you > given your schedule. May I please know why I cannot access the mailing > lists ? If I can exchange views with other experienced NETCDF Fortran > developers that would be completely adequate. I think access to the netcdfgroup mailing list is working again. Please try http://www.unidata.ucar.edu/mailing_lists/archives/netcdfgroup/index.html and let us know if you still have problems accessing it. > Russ - unfortunately that file is 157 mega bytes. Yes I can view it with > ncdump all right. I can give you the location of the source files and how > to build it(it is available on net) It does not dump the core file to disk. > So therefore I cannot load it into gdb. Yes I can view other netcdf files > without a coredump. > > Here is a sample of the error message I get - > Segmentation fault (core dumped) > ********************************************************* > * def_anomaly * > ********************************************************* > forrtl: severe (24): end-of-file during read, unit 10, file > /home/aswin/potentialVorticity/data/inp/fort.10 > To reproduce and diagnose the problem, we need either a small example file or a small program that demonstrates the problem. The error message about a segmentation fault in a program external to the netCDF library is not sufficient. Thanks. --Russ > address@hidden> wrote: > > > Hello Ashwin, > > > > Are you able to load the generated core file into gdb? If so, that may > > provide some information about what is crashing and where. > > > > Besides this, answering the following questions may help narrow down what > > is going on: > > > > 1. Can you open other netcdf files without a core dump? > > 2. Can you read this file with the `ncdump` command-line command, or other > > netCDF-aware programs? > > > > It sounds like the file may be corrupt, but we should be able to figure > > that out. If the file is relatively small, can you provide a copy of it > > for me to look at? > > > > -Ward > > > > Also, appending data to an existing netCDF file is possible. Adding data > > to an existing variable requires that the variable have an "unlimited" > > dimension, and that the data be added along that dimension. Appending new > > metadata or additional new variables can be significantly more efficient > > with a netCDF-4 file. > > > > --Russ > > > > > > > > > Hello , > > > I am getting core dumps when I am reading in a netcdf file > > > using netcdf fortran 4.4.0. My compiler is ifort. Can you give me some > > > clues to help me debug this problem ? > > > When I turn on gdb and run it I get a message saying end of file reached. > > > > > > Regards, > > > Ashwin. > > > > > > > > > When I go to this site - I get 503 Service Temporarily available - > > > > > https://www.unidata.ucar.edu/mailing_lists/archives/netcdfgroup/2013/msg00357.html > > > > > > If I had an existing file and I have to append data to an existing NETCDF > > > dataset is there a problem with doing that ? > > > > > > address@hidden> wrote: > > > > > > > > > > > ashwinD12 ., > > > > > > > > Your Ticket has been received, and a Unidata staff member will review > > it > > > > and reply accordingly. Listed below are details of this new Ticket. > > Please > > > > make sure the Ticket ID remains in the Subject: line on all > > correspondence > > > > related to this Ticket. > > > > > > > > Ticket ID: SPN-205342 > > > > Subject: Netcdf with ifort > > > > Department: Support netCDF > > > > Priority: Normal > > > > Status: Open > > > > > > > > > > > > > > > > The NetCDF libraries are developed at the Unidata Program Center, > > > > in Boulder, Colorado, funded primarily by the National Science > > Foundation. > > > > > > > > All support requests are handled by the development team. No dedicated > > > > support staff are funded at this time. For this reason we cannot > > guarantee > > > > response times, nor that we can resolve every support issue, although > > we > > > > do our best to respond within 72 hours. > > > > > > > > It is in the nature of support requests that the same question is asked > > > > many > > > > times. We urge you to search the support archives for material > > relating to > > > > your support request: > > > > > > > > http://www.unidata.ucar.edu/search.jsp?support&netcdf > > > > > > > > If you are having trouble building netCDF, please take a look at the > > > > "Building NetCDF" page: > > > > > > > > http://www.unidata.ucar.edu/software/netcdf/docs/building.html > > > > > > > > or the (unfortunately somewhat out-of-date) NetCDF Build Troubleshooter > > > > page: > > > > > > > > http://www.unidata.ucar.edu/software/netcdf/docs/troubleshoot.html > > > > > > > > Windows users should see the FAQ list: > > > > > > > > > > http://www.unidata.ucar.edu/software/netcdf/docs/faq.html#windows_netcdf4_2 > > > > > > > > Complete documentation (including a tutorial, and sample programs in C, > > > > Fortran, > > > > Java, and other programming languages) can be found on the netCDF > > > > Documentation page: > > > > > > > > http://www.unidata.ucar.edu/software/netcdf/docs/ > > > > http://www.unidata.ucar.edu/software/netcdf/examples/programs/ > > > > > > > > If you resolve your issue through one of these methods, please send a > > > > reply to > > > > this email, letting us know that you no longer need support. This will > > help > > > > us spend more time on netCDF development. > > > > > > > > Best regards, > > > > > > > > Unidata User Support > > > > > > > > > > > > > > > > > > Russ Rew UCAR Unidata Program > > address@hidden http://www.unidata.ucar.edu > > > > > > > > Ticket Details > > =================== > > Ticket ID: SPN-205342 > > Department: Support netCDF > > Priority: Normal > > Status: Closed > > > > > > Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: SPN-205342 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.