[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #40267] imread ('default.img') causes segfault
From: |
Carnë Draug |
Subject: |
[Octave-bug-tracker] [bug #40267] imread ('default.img') causes segfault |
Date: |
Sun, 20 Oct 2013 17:10:08 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130917 Firefox/17.0 Iceweasel/17.0.9 |
Follow-up Comment #2, bug #40267 (project octave):
1) yes.
2) fixed with cset 292319fb7fcc. Took me a while to get the cause of it
because the reading was already in a try/catch block and I couldn't understand
why it was not being caught. the exception was being thrown from the call to
ping().
3) Because GM can do it. Try the following:
echo "hello world" > img.txt
gm identify img.txt
gm display img.txt
If you take a closer look to that "all white image", you'll notice that it
also has the words "hello world" in black somewhere. I can see them with
imshow().
We are relying on GM to decide what it can read and not. We could blacklist
some of the coders though. By the way, GM should be able to read matlab files
as well. See http://www.graphicsmagick.org/formats.html
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?40267>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/