hm... a closer look at ufraw reveals that the same out of bounds accessing is
used for different enumeration values.
I must admit, that -- while that's legal from a C perspective -- I think it's
not a too good idea to use out of bounds values for the enums in ufraw.
I guess it would be a better idea to get ufraw fixed, instead of
applying band-aid patches to lensfun. I'll attach a patch against the
ppa package of ufraw that hopefully fixes the problem. Can you check if
that works, and if so, forward it to ufraw authors?
Are you ok, if I'll mark the bug in lensfun invalid if this works out?
Cheers,
Stefan.
** Attachment added: "ufraw.patch"
http://launchpadlibrarian.net/32242648/ufraw.patch
--
[regression] lensfun 0.2.3-0ubuntu4 freezes UFRaw.
https://bugs.launchpad.net/bugs/433368
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
