Bug#626019: libsane-perl: Proposal on how to track this down

[Willi Mann]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi Jeffrey!

How much work would it be to write a C program that does the same
calls to libsane as the partly failing test in libsane-perl does? My
idea is to analyze this program with Helgrind (valgrind), in the hope
to find a race condition. If such a race condition could be
identified, this race condition could clearly be attributed to libsane
- - and hopefully being fixed easily.

With perl being involved the helgrind output is quite unreadable, as
there are a lot of warnings related to perl.

Willi
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBCAAGBQJPr+6WAAoJEIy+IZx0V22Bx/YQAITS/azJFiQ8UtPEsTEMCumy
rs8allKC3whXxoF1/Pn3ZaRwyJSQM+LAyHouBAM1A/dK3AdwYzC533XzU63MvJX0
EZekvuujRdQiIUVjD7hCx8pJqUSg7cycAB/MTHQLW5MFflFa0xZCOe2X+Tsi5bWW
HJ5Y67PIUQ7KxeFK3G9+Za+u4Aqw+oVnk27wZxL3yjWFYZInCzOsBgN9+Lz51yON
C2Rqb5IBP4pl5Trf+TACFgKATK2cA/zp9ESrLzcs5F7e0ARbTeCYjfteKy6eJiZq
6E3fkCIwhYkiXa6rQSZWV76N+tmO0NeH2C6BvusICkl9RoWneJPLtqqt6UEx+rx4
OQuNUtZ018wrjZ+1rfNEYVrpx4UHYkjmkpy3PNwBHM9A6Qxfzzu1Hebpicsj/ats
liqnbvPPHKa+Z7z6ppcUjfE4SgrbDJ+C5yDWu+YOdXpllUrX1Tx9xmthI1MrbctZ
SG4uugnvdrFc2yWHyn1a1D+tt9xeEojChdj2BJcoFEZoT0RbHEZiggVR5gVSSJGR
ROdCwtIDFljhOkh/8PkuuAF0c2i8YDF9TBLk/gm9pCSYDsNVDu3A53Bi+SZh4+rY
e3R+CMaswSJWW7+JQ66VogvZe7VsvcWuLZF9J19GN7PRi0HaxnUnh04LRvBr1Z8f
y+hjIyxkNbPTfPBs59YH
=UkQR
-----END PGP SIGNATURE-----