|
From: | Carnë Draug |
Subject: | [Octave-bug-tracker] [bug #41699] imread causes a segmentation fault on Windows with "clear all" or when Octave exits |
Date: | Wed, 04 Feb 2015 11:06:14 +0000 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 Iceweasel/31.4.0 |
Follow-up Comment #55, bug #41699 (project octave): It does not segfault on 3.9.0+ when doing that because of memlock, but it still crashes when exiting Octave right? Can you go through the imformats file in 3.8.2, and comment/uncomment the lines, while doing `imformats (); clear all;` until you find what exactly is causing the sefgault? We thought that the cause were the function handles to the private functions __imwrite__ etc. If it is not, you will have find that for us (I can't replicate this bug, I do not have windows). _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?41699> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |