|
From: | Dan Sebald |
Subject: | [Octave-bug-tracker] [bug #54180] libinterp/corefcn/file-io.cc-tst failure and weird output when test suite is run twice |
Date: | Mon, 25 Jun 2018 15:32:15 -0400 (EDT) |
User-agent: | Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0 |
Follow-up Comment #12, bug #54180 (project octave): Here's a new changeset that adds various unwind_protect blocks. Let me know if it as least on the target somewhere. In some cases the fclose() doesn't have any commands prior to it that will error, so those don't need to be protected. There are a few others near the end for which the fclose could possibly moved earlier and avoid the need for an unwind_protect--in fact, those might use the same "nm = tempname (); ... unlink(nm)" approach to not leave the small temporary files hanging about. But I do leave the temporary file around when there is an error in case someone needs to debug by looking at that file contents. (file #44435) _______________________________________________________ Additional Item Attachment: File name: octave-fclose_missing_from_io_test-djs2018jun25.patch Size:12 KB _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?54180> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |