Hello,
I've been facing a mysterious bug, and I wanna know if anyone already 
experienced something like that or have a clue about whats going on?
The applications has several windows accessible through buttons in the main 
screen. After some time using I can't open windows anymore, and in the error 
log I got the following:

XRequest.56: BadLength 0x0
XRequest.4: BadLength 0x0
XRequest.0: BadRequest 0x0
XRequest.0: BadRequest 0x0
XRequest.4: BadLength 0x0
XRequest.42: BadLength 0x0
XRequest.42: BadLength 0x0
XRequest.42: BadLength 0x0
XRequest.42: BadLength 0x0
XRequest.2: BadLength 0x0
XRequest.42: BadLength 0x0
XRequest.4: BadLength 0x0
XRequest.47: BadLength 0x0
XRequest.4: BadLength 0x0
XRequest.26: BadLength 0x0
XRequest.43: BadLength 0x0
XRequest.18: BadValue 0x12
XRequest.2: BadLength 0x12

after a while I think other thinks got confused:

XRequest.40: BadWindow 0x21
XRequest.53: BadAlloc 0x64bc91
XRequest.70: BadDrawable 0x64bc91
XRequest.70: BadDrawable 0x64bc91
XRequest.70: BadDrawable 0x64bc91
XRequest.70: BadDrawable 0x64bc91
XRequest.70: BadDrawable 0x64bc91
XRequest.70: BadDrawable 0x64bc91
XRequest.70: BadDrawable 0x64bc91
XRequest.70: BadDrawable 0x64bc91

Just to inform, this bug is very hard to reproduce, and also I'm using 
Xfbdev(tinyx) with fltk-1.3.x-r6581 and linux.
I can see three reasons for this bug. The first could be some memory fail, 
which can damage the packets, the other could be fltk or Xserver getting 
confused to handle communication packets. The third and most probable is that 
my application should be using some bad practice in fltk.
Does anyone have a clue?

Thanks in advanced,

J.Marcelo Auler


_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk

Reply via email to