On Fri, Mar 12, 2004 at 05:56:10PM +0100, Emmanuel Fleury wrote: > So, my guess is that *something* is happening in _XReply (or around this > function) that cause the problem... > > ====== > _XReply (dpy=0x84af750, rep=0xbffff420, extra=0, discard=0) at > XlibInt.c:1670 > 1670 if(dpy->lock && > (gdb) > 1674 dpy->flags |= XlibDisplayReply; > (gdb) > 1682 if (!dpy->lock || !dpy->lock->reply_was_read) > (gdb) > 1684 (void) _XRead(dpy, (char *)rep, > (long)SIZEOF(xReply)); > ====== > > Here: > (long)SIZEOF(xReply) = 32 (and not 864 as it should be) > > Any idea to allow me to go further ??? Not really. > How are managed the network transferts in X ? That code lives in xc/lib/xtrans. > What should I compile with the debug option to get some informations > about this problem of information leak ? Xtransint.h says: /* * XTRANSDEBUG will enable the PRMSG() macros used in the X Transport * Interface code. Each use of the PRMSG macro has a level associated with * it. XTRANSDEBUG is defined to be a level. If the invocation level is =< * the value of XTRANSDEBUG, then the message will be printed out to stderr. * Recommended levels are: * * XTRANSDEBUG=1 Error messages * XTRANSDEBUG=2 API Function Tracing * XTRANSDEBUG=3 All Function Tracing * XTRANSDEBUG=4 printing of intermediate values * XTRANSDEBUG=5 really detailed stuff #define XTRANSDEBUG 2 * * Defining XTRANSDEBUGTIMESTAMP will cause printing timestamps with each * message. */ You will need to recompile Xlib (libX11), the X server, or both with this symbol defined to enable the debugging. -- G. Branden Robinson | Damnit, we're all going to die; Debian GNU/Linux | let's die doing something *useful*! branden@debian.org | -- Hal Clement, on comments that http://people.debian.org/~branden/ | space exploration is dangerous
Attachment:
signature.asc
Description: Digital signature