|
From: | Mike Miller |
Subject: | [Octave-bug-tracker] [bug #41699] imread causes a segmentation fault when exiting Octave |
Date: | Tue, 22 Apr 2014 13:46:50 +0000 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.152 Safari/537.36 |
Follow-up Comment #28, bug #41699 (project octave): Since I'm not that familiar with Windows, can you verify that the value was propagated into Octave by running "getenv OMP_NUM_THREADS" at the Octave prompt? It should say "ans = 1". If not, then try "setenv OMP_NUM_THREADS 1" within Octave. If that's not fixing your crash, then we are back to this being unrelated to the segfault I see on Linux. _______________________________________________________ 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] |