Hi Joel, > The code I'm working on for a time-sensitive program release, so I greatly > appreciate any and all help you can offer. > > Any thoughts on what I might be doing wrong with the netcdf library that is > causing it to crash? Let me know if you need any additional information > from me or if you need me to take any debugging steps. The valgrind output you sent indicates possible problems with the calling program, before NF90_enddef is called, and that may be the source of the later null pointer problem valgrind is showing. That's about as much as can be gleaned from valgrind output, without knowing any other information about your platform, the version of netCDF and HDF5 used, how the library was built, or whether you ran "make check" before installing. My advice is to first correct the use of uninitialized variables indicated by valgrind, looking especially for something that might result in an unitialized pointer or unallocated memory in the calling program. It's likely that the later null pointer error from the NF90_enddef call will disappear after the earlier errors are addressed. If you're still seeing the same problem, make sure you have run "make check" on the netCDF Fortran library after building from source, because it tests all the F90 functions, including NF90_enddef. If that works OK, try to construct a small program that demonstrates the error you are seeing and would allow us to reproduce it here. We would also need information on the versions of libraries used and the config.log generated when the netCDF Fortran library was built. --Russ > address@hidden> wrote: > > > > > Joel Scott, > > > > 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: QYP-982325 > > Subject: NetCDF fortran enddef crashing program > > 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: QYP-982325 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.