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

2012-05-15 Thread Jeffrey Ratcliffe
On 14 May 2012 22:48, Willi Mann wrote: >> I am in half a mind to disable the tests and then deal with any >> bug reports from the problematic archectures. At least there then >> might be a user on a suitable machine and motivated to help. > > At least for the wheezy release, this sounds like a sa

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

2012-05-14 Thread Willi Mann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi! Am 2012-05-14 20:37, schrieb Jeffrey Ratcliffe: > It is certainly doable, but my first problem is that I have not > managed to reproduce the issue. As I already said in the bug report, I could reproduce the issue on one of my amd64 (Linux) sys

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

2012-05-14 Thread Jeffrey Ratcliffe
It is certainly doable, but my first problem is that I have not managed to reproduce the issue. If I could get access to a machine which reliably reproduced the problem, it would certainly be quicker to add some print statements to the .xs to work out what was going on rather than spend time on po

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

2012-05-13 Thread 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 suc