octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #63714] uitable may show nan with data=zero


From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #63714] uitable may show nan with data=zero
Date: Sun, 29 Jan 2023 13:11:27 -0500 (EST)

Update of bug #63714 (project octave):

                  Status:                    None => Ready For Test         

    _______________________________________________________

Follow-up Comment #8:

"Still some warnings from TSAN."

Yeah, I think there are still many threading problems with the way the
graphics objects are handled.

I don't see any reason not to make this change on stable, so I'll do that much
at least.

There is another call to warning in Table.cc in the function qStringValueFor:


    else
      {
        std::stringstream warn_string;
        warn_string << "Unknown conversion for datatype " << val.class_name
()
                    << " to " << format
                    << " for value " << val.string_value (true);
        warning ("%s", warn_string.str ().c_str ());

        text = Utils::fromStdString (val.string_value (true));
      }


I don't understand this code well enough to see how that warning can be
triggered, but ultimately the result appears to be that an attempt is made to
convert an octave_value to a string.  Given that the call to warning is not
safe at this point, it seems best to just eliminate it.

I pushed the following change on stable and merged with default:

http://hg.savannah.gnu.org/hgweb/octave/rev/abe72b9464d6


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?63714>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]