Bug#234556: xlibs: many clients get BadLength error from X_ChangeProperty request

[Emmanuel Fleury <fleury@cs.auc.dk>]

Can somebody explain to me the meaning of "Address 0x30c out of bounds"
in gdb ????

I think I get two of these nice babies in the code:


When writing to the socket:

On Thu, 2004-02-26 at 16:50, Emmanuel Fleury wrote:
> (gdb) 
> _X11TransWrite (ciptr=0x83b0cf0, buf=0x83b0cf0 "@g\023@\003",
> size=138087664) at Xtrans.c:843
> 843	    return ciptr->transptr->Write (ciptr, buf, size);
> (gdb) 
> _X11TransSocketWrite (ciptr=0x83b0db0, buf=0x83b0db0 "<\001\002", 
>     size=138087856) at Xtranssock.c:1750
> 1750	    return write (ciptr->fd, buf, size);
> (gdb) 
> 1744	{
> (gdb) 
> 1750	    return write (ciptr->fd, buf, size);
> (gdb) 
> 1752	}
> (gdb) 
> _X11TransWrite (ciptr=0x30c, buf=0x30c <Address 0x30c out of bounds>,
> size=780)
>     at Xtrans.c:844
> 844	}


And then, when reading from the socket (which seems to be normal as we
put it into the socket like this, I guess...):

> _X11TransSocketRead (ciptr=0xbffff4f0, buf=0xbffff4f0
> "\020A*@`\\8\bD\001",  size=-1073744656) at Xtranssock.c:1736
> 1736	    return read (ciptr->fd, buf, size);
> (gdb) 
> 1730	{
> (gdb) 
> 1736	    return read (ciptr->fd, buf, size);
> (gdb) 
> 1738	}
> (gdb) 
> _X11TransRead (ciptr=0x20, buf=0x20 <Address 0x20 out of bounds>,
> size=32)
>     at Xtrans.c:837
> 837	}
> (gdb) 


My guess is that it is the cause of the error message (I had hard time
to get through all these functions... ^_^). But I might be wrong of
course.

Now, what is puzzling me is: 

"What is the cause of this address out of bounds ???"

At least, it is highly reproducible once I get my laptop stuck in this
strange mode... I hope I'm getting closer !

Regards
-- 
Emmanuel Fleury

Computer Science Department, |  Office: B1-201
Aalborg University,          |  Phone:  +45 96 35 72 23
Fredriks Bajersvej 7E,       |  Fax:    +45 98 15 98 89
9220 Aalborg East, Denmark   |  Email:  fleury@cs.auc.dk