On Sun, 13 Jun 2004, Branden Robinson wrote: > On Thu, Jun 10, 2004 at 06:17:50PM -0400, Thomas Dickey wrote: > > On Fri, May 28, 2004 at 10:27:16PM -0500, Branden Robinson wrote: > > > > > > Okay, I will be patient while you explore this. > > > > > > Just as a remark to myself and my fellow "debian-x"ers, if it turns out > > > the bug is in Xt, this bug should be reassigned to libxt6. > > > > As far as I can determine, the bug is in the X libraries. Running against > > the XFree86 4.3.0 build tree, I can reproduce the bug. Running against > > XFree86 4.4.0 I cannot reproduce the bug. This is independent of the > > version of xterm, and since it appears to have been fixed in the later > > X libraries indicates to me that it should be reassigned to libxt6. > > Are you reasonably confident that it's Xt that has been fixed upstream > or is that just a guess? I.e., could it be Xlib insteaad? Which way > would you bet?
It's only a guess. I don't see any reason why (don't know that there are interface changes) one couldn't mix the 4.3/4.4 Xlib, Xt, Xmu libraries to point to a specific library which is most likely the cause. That might be more efficient than building whole snapshots from different dates. What I normally do on fishing expeditions like this is to do a binary search with the snapshot dates to narrow it down. (It's also possible that the problem exists in 4.4 but is obscured by something else). > It's not a really big deal, but I'm trying to get as much data as > possible in case someone else wants to sink their teeth into this. > > (That might be me, armed with a diff of xf-4_3-branch and xf-4_4_0.) > > -- > G. Branden Robinson | I'm not going to waste my precious > Debian GNU/Linux | flash memory with Perl when I can > [EMAIL PROTECTED] | do so much more with it. > http://people.debian.org/~branden/ | -- Joey Hess > -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net
