> Have other folks' experiences with libsane-pnm been generally positive or
> negative?
Negative. It is buggy as hell. I am fixing this, but I have almost no time
to do it. Someone added really hard-to-implement options (like the
geometry stuff) there, and then didn't do it right.
Of course I get the bad credits for that, as I'm listed as the author.
> I keep discovering inconsistencies in it, and it generally seems
> to not work as advertised. In particular:
Yes. I'm fixing that.
> * it seems to segfault in sane_read sometimes (Linux 2.0.36). I've checked
> to make sure that my memory blocks are all getting allocated. I realize
> that I might be having some problems since I'm writing inside of an XSUB,
> and there may be perl wackiness going on. However, libsane-umax doesn't
> segfault :-)
No. There are many big bugs in the memory handling. If you are not requesting
the "right" assumed length of data, it's very likely to segfault ...
> * when three-pass is set to true, I get GREEN frames over and over, and
> never get anything else. I'm calling sane_start after I get the EOF flag
> for each frame, but still get the danged GREEN frames.
ARGL. O.K. - I'll try to get at it at the weekend.
> For what it's worth, xv renders my sample PNM file properly, so I assume
> that it's clean.
Yeah. The pnm source is buggy as hell.
CU, Andy
-- Andreas Beck | Email : <Andreas.Beck@ggi-project.org>
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com