paul.sz...@sydney.edu.au wrote: > Looking at the code around line 181 in ClientChannel.C where the > crash happened, seems to me that format should have one of the > values 8, 32 and maybe 16. Re-writing the code to explicitly test > for format==16 so: > > . . . > > I do not quite understand X protocol and do not know how to handle > the format==6 case: cannot be "lumped in" with the format==8 case, > as changing the line > > - if (format == 8) > + if ((format > 0) && (format <= 8)) > > seems to cause dxpc to "run away" with 100%CPU. > > Can someone help please? > > Thanks, Paul > > Paul Szabo p...@maths.usyd.edu.au http://www.maths.usyd.edu.au/u/psz/ > School of Mathematics and Statistics University of Sydney Australia
Have you contacted the upstream author? You can find his contact information at http://www.vigor.nu/dxpc. This project hasn't been under active maintenance for many years, but in my previous correspondence with him, he has been responsive. I don't know the code or X protocol well enough to help debug this in the amount of time I have, but if he or you comes up with a good patch, I will certainly be happy to apply it to the debian package. -- Jay Berkenbilt <q...@debian.org> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
