While testing sane python bindings I found a segmentation fault while trying to open the device. I attach a couple of logs.
'sane.log' is the output of running: SANE_DEBUG_HP5590=50 SANE_DEBUG_SANEI_USB=255 ./test-sane.py 'valgrind.log' is the output of running my test script with "valgrind --trace-children=yes" The script is very simple (the device exists): import sane sane.init() sane.open( 'hp5590:libusb:004:005' ) This is running Debian unstable with the following packages: python-imaging-sane 1.1.6 sane 1.0.14 libsane 1.0.19 plus -deb packages, as as you can see in valgrind.log Do you think this is a Debian specific problem, any other tests I could make? -- Albert Cervera i Areny http://www.NaN-tic.com -------------- next part -------------- A non-text attachment was scrubbed... Name: sane.log.bz2 Type: application/x-bzip2 Size: 3890 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080615/e1c7c0a7/attachment.bin -------------- next part -------------- A non-text attachment was scrubbed... Name: valgrind.log.bz2 Type: application/x-bzip2 Size: 4820 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080615/e1c7c0a7/attachment-0001.bin
