|
From: | Doug Stewart |
Subject: | [Octave-bug-tracker] [bug #39925] imagesc crash |
Date: | Tue, 22 Oct 2013 14:58:19 +0000 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/30.0.1599.101 Safari/537.36 |
Follow-up Comment #24, bug #39925 (project octave): I see now that 1e17 + 1 =1e17 we have reached the limit of our precision. So the original problem at 1e10 has disappeared Now what I see is that if we do 1e17 for the x axes then it crashes but if we do 1e17 for the y axes then we get an out of memory error. Why the difference???? _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?39925> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |