RCS/NML Bugs

How to report RCS and NML Bugs or get support:

I can not guarantee to be able to provide support, whether I can or not depends on what projects I am working on as well as how many reports/questions arrive around the same time and the availability of various computer resources, however I do intend to at least try.

Create an email with the following information.

• A description of the problem.
• The exact version of RCS library being used. If this is being run on a NIST computer this might be whatever is installed in a given directory on given host otherwise I need the name of the tar.gz file it came from, or you can check rcsvers.hh
• The operating system, compiler and CPU architecture.
• A log of any compiler or run-time error messages produced. If it is more than a page or two I ussually want the first page with errors. If it involves a graphical tool you can usually get a screen shot by pressing the print screen key, saving to a file and attach that to the email.
• The name of the project and how/if it impacts NIST or the US Federal Government. If someone else on the same project contacts me sometimes it is useful to be able to make the connection. I also hate to play favorites, but someday it might be necessary to make sure the NIST related problems are solved first.
• If any of the information needs to be kept secret to protect intellectual property, privacy or security, please let me know otherwise I would like to post at least the more interesting bugs or questions and thier resolution on the website.
• If you can create a simple program than demonstrates the problem without requiring any special hardware/software that is not widely/freely available and you can send me the source for that it might be very helpful.
• The NML configuration file is often helpful.

Send the email to shackle [at] nist.gov (shackle[at]nist[dot]gov).

Do not be afraid to send additional emails a couple of days later if you do not get a response or an excessively terse one. I might have more time a couple of days later but I do not ussually go back to the old emails since it is likely the problem was by that time solved or completely given up on.

---

Previously reported problems:

Opening NML channel mapsout...done 
initialize maps we need to start nav data first 
nml.cc 155: !ERROR! void *NML::operator new() called with size (336) < sizeof(NML) (616) the code calling NML was probably not compiled with the correct header file version.

I still can run the program even I got the above error. 

This is typically caused by compiling with -I pointing to the headers for one version 
of NML and linking with another version or changing the rcslib version between the time 
f the compile and the link if rcslib is statically linked or between the compile 
and the run if the library is dynamically linked. You might theoretically run anyway, but 
it is probably a good idea to clean this up. 

---

Software Disclaimer

This software was produced by the National Institute of Standards and Technology (NIST), an agency of the U.S. government, and by statute is not subject to copyright in the United States. Recipients of this software assume all responsibility associated with its operation, modification, maintenance, and subsequent redistribution.