On Mon, Aug 07, 2006 at 09:59:21AM -0700, Guy Harris wrote: > > Yes, you're absolutely right. I didn't thought about that. Major > > opcode returned by XQueryExtension is a dynamic value and depends from > > load order of X11 server extension modules. > > > > So, there is no solution 'in general'. But X11 dissector maintains > > extensions table (which built according XQueryExtions replies). Is > > there standard way in Wireshark to 'publish' such table from dissector > > module to others? > > > > As you've noted, X11 extensions have more or less standard names, so > > my module can query X11 dissector for GLX major_opcode value. > > Probably the best way to do this would be to register extension > dissectors using the extension *name*, and, for an X request with a > request code >= 128, attempt to look up the request code in the > extensions table and, if it finds the extension name, call > dissector_try_string() with the extension name. Yes, this really looks much better, thank you for advice. Best regards, -- Max Lapan <lapan_mv@xxxxxxxx>, +7(0855)296471, ICQ: 233841810 PGP Fingerprint: 0C47 91E3 35BA 3E6D 64D5 5740 6F3C A37F C112 4765 HPC Architect/Administrator, Engineering Analysis Systems Department JSC Saturn http://www.npo-saturn.ru
Attachment:
signature.asc
Description: Digital signature