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

Re: 971208: Bug when creating float attribute

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: Re: 971208: Bug when creating float attribute
  • Date: Mon, 08 Dec 1997 12:26:19 -0700
> From: Tom LeFebvre <address@hidden>
> To: Russ Rew <address@hidden>
> Subject: Bug when creating float attribute

Hi Tom,

> We've recently bumped into a bug when creating a float attribute of a
> netCDF variable.  The value of the attribute is fine right before we
> create the new attribute, but when we call var->add_att(const char *,
> float) the value in the netCDF file is 0.0.  We also get an
> uninitialized memory read (UMR) from Purify during the execution of
> add_att. 
> 
> Has this bug been reported before and if so, is there a patch for it?
> If not, I'd be happy to whip up a small piece of code that
> demonstrates the bug and send it to you.  Thanks!

Nope, we haven't seen that one before.  If you can construct a small
example demonstrating the problem, we'd appreciate it.  Thanks.

--Russ