Bug#418021: Bug #418021

2007-04-06 Thread ldoolitt
eyck -

As the author of the patch that apparently broke your application,
this report totally baffles me.  Can you confirm that downgrading
to libx11-6 version 2:1.0.3-6 removes the problem?

Are you able to patch and rebuild test versions of libx11?
If so, one quick thing to try is to put back the
|| image_bytes_per_line < 0
snippet on lines 336 and 405; the first of those will avoid leaking
memory in previously detectable erroneous image_bytes_per_line.

It would also be interesting to put a fprintf(stderr,"libx11-debug:
%d", image_bytes_per_line, min_bytes_per_line); right before lines 378
and 422, assuming the message goes someplace where you can see it.
Or you could set a breakpoint on those lines with gdb, and print out
those variables (assuming they're not optimized away).

Can you give instructions for me to reproduce this bug on my machine?
Preferably without needing an account on an NT/2000 remote.

- Larry


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#418021: Bug #418021

2007-04-06 Thread Steve Langasek
On Fri, Apr 06, 2007 at 08:57:45AM -0700, [EMAIL PROTECTED] wrote:
> eyck -

> As the author of the patch that apparently broke your application,
> this report totally baffles me.  Can you confirm that downgrading
> to libx11-6 version 2:1.0.3-6 removes the problem?

C.f. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=418016;msg=24 for a
crash in another application related to this change.  That one may reduce to
a bogus assumption about bpp vs. bit depth.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
[EMAIL PROTECTED]   http://www.debian.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]