Bug#399119: recompiled libsane with debugging symbols and stepped through the code...

2006-12-19 Thread Michal Sabala
On 2006/12/18 at 13:02:16 Julien BLACHE <[EMAIL PROTECTED]> wrote > Michal Sabala <[EMAIL PROTECTED]> wrote: > > Hi, > > > Following is the part of epson.c driver that fails, in my case, buf[0] > > contains 0xb0. Original poster also had 0xb0 in the beginning of the 88 > > byte buffer. > > > > 06

Bug#399119: recompiled libsane with debugging symbols and stepped through the code...

2006-12-19 Thread Julien BLACHE
Michal Sabala <[EMAIL PROTECTED]> wrote: Hi, > handling MFPs differently. Anyways, the patch works with Epson CX5200 > (all scanning modes, color depths, etc. _do_ work) and it should not > negatively affect any other device. Hmm, it'll have to go through upstream because I can't tell :/ > And

Bug#399119: recompiled libsane with debugging symbols and stepped through the code...

2006-12-18 Thread Julien BLACHE
Michal Sabala <[EMAIL PROTECTED]> wrote: Hi, > Following is the part of epson.c driver that fails, in my case, buf[0] > contains 0xb0. Original poster also had 0xb0 in the beginning of the 88 > byte buffer. > > 06144 receive (s, buf, len, &status); /* reveive actual status > data */ > 061

Bug#399119: recompiled libsane with debugging symbols and stepped through the code...

2006-12-18 Thread Michal Sabala
Package: libsane Version: 1.0.18-3 Followup-For: Bug #399119 I had my Epson CX5200 working correctly with libsane 1.0.17. Last night I upgraded to 1.0.18 and now I have exactly the same problem as original poster. Following is the part of epson.c driver that fails, in my case, buf[0] contains 0xb