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

[netCDF #LDE-989755]: request for assistance: strange runtime messages

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 #LDE-989755]: request for assistance: strange runtime messages
  • Date: Wed, 17 Jun 2009 05:45:54 -0600
> Hello,
> 
> I have a question. I have installed NetCDF 4 and reading a NC file into
> a C structure using the C-functions. All goes well, but at runtime I get
> a deluge of messages in stderr, some of which I have pasted below.I
> don't get these messages when I run the same code without the bit using
> the NC functions. I do not get any explicit errors and my code runs
> fine, so I was wondering if you could help me figure out what the issue
> is. I can send you the code if you require.
> 
> Thanks a lot!
> 
> Kamen Kozarev
> 
> 
> 16659:        binding file /home/kamen/svn/emmrem/trunk/src/eprem [0]
> to /lib/libc.so.6 [0]: normal symbol `time' [GLIBC_2.2.5]
> 16659:        binding file /home/kamen/svn/emmrem/trunk/src/eprem [0]
> to /lib/libc.so.6 [0]: normal symbol `access' [GLIBC_2.2.5]
> 16660:        binding file /home/kamen/svn/emmrem/trunk/src/eprem [0]
> to /usr/lib/libnetcdf.so.4 [0]: normal symbol `nc_open'
> 16663:        binding file /home/kamen/svn/emmrem/trunk/src/eprem [0]
> to /lib/libc.so.6 [0]: normal symbol `tim
> 16660:        binding file /usr/lib/libnetcdf.so.4 [0]
> to /usr/lib/libnetcdf.so.4 [0]: normal symbol `nc__open_mp'
> 16660:        binding file /usr/lib/libnetcdf.so.4 [0] to /lib/libc.so.6
> [0]: normal symbol `malloc' [GLIBC_2.2.5]
> 16660

Howdy Kamen!

Wow, these are weird messages. I note that they are neither errors nor 
warnings. The loader is telling you where it is finding each function, and not 
just netcdf functions, but also C library functions.

Does this happen without netCDF? Try commenting out all the netcdf code in your 
program, but leave in a call to a math function like floor. Now link with -lm 
and without -lnetcdf. Do you see the same problem?

Did you install netCDF from source on this machine? If so, did this problem 
occur when the test programs were compiled for "make check"?

Thanks,

Ed


Ticket Details
===================
Ticket ID: LDE-989755
Department: Support netCDF
Priority: Normal
Status: Open


--AC2B7CB19B.1245239162/laraine.unidata.ucar.edu--