|
From: | Markus Mützel |
Subject: | [Octave-bug-tracker] [bug #57435] Test suite crashes on Windows on sparse.tst |
Date: | Sat, 21 Dec 2019 19:06:36 -0500 (EST) |
User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0 |
Update of bug #57435 (project octave): Status: None => Patch Submitted _______________________________________________________ Follow-up Comment #22: I cross-compiled with the attached patch (and SuiteSparse 4.5.6). The test suite now completes without Octave closing unexpectedly. Wrt Rik's comment #21: I believe this is what I did with the last 2 verbatim blocks in comment #18. Before "clear functions", the pointers in the SuiteSparse_config struct are valid and resolve to the functions as set in amd.cc. After "clear functions", the pointers still have the same values. But they point to invalid memory. I'll try if I can get a newer version of SuiteSparse to cross-compile. But I think that the problem is caused by Octave setting function pointers in the global structure that can get out of scope. The mlock is necessary. Or the functions shouldn't be (un-)loadable and moved to Octave core like jwe suggested. (file #48099) _______________________________________________________ Additional Item Attachment: File name: bug57435_suitesparse_mlock.patch Size:2 KB <https://savannah.gnu.org/file/bug57435_suitesparse_mlock.patch?file_id=48099> _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?57435> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |