Re: [Wireshark-dev] I want to pop up a window when http dissector dissect some kind of payload

于 2010年12月14日 13:21, Bill Meier 写道: > On 12/13/2010 10:41 PM, 刘昆 wrote: > >> If I want to pop up a window when http dissector dissect some kind of >> payload,where can I write the gtk code ? >> > > As Guy Harris already indicated to you when you asked this question > previously: > > "

Re: [Wireshark-dev] I want to pop up a window when http dissector dissect some kind of payload

I am just guessing, but sometimes it would be nice to see the http payload without the hex dump and formatted kind of nicely. Sent from my iPad On Dec 14, 2010, at 12:21 AM, Bill Meier wrote: > On 12/13/2010 10:41 PM, 刘昆 wrote: >> If I want to pop up a window when http dissector dissect some k

Re: [Wireshark-dev] I want to pop up a window when http dissector dissect some kind of payload

On 12/13/2010 10:41 PM, 刘昆 wrote: > If I want to pop up a window when http dissector dissect some kind of > payload,where can I write the gtk code ? As Guy Harris already indicated to you when you asked this question previously: "You should solve the problem by not using GUI functions in

Re: [Wireshark-dev] Automatic test for a dissector DLL

Am 13.12.2010 23:52, schrieb didier: >> tshark -V -r sample_file.pcap >> >> Unfortunately I get the whole tree. I failed to specify that only my >> dissector's output is reported. >> >> How can I limit the output to one protocol level. As an example the TCP >> level would be great (without IP, Ethe

[Wireshark-dev] I want to pop up a window when http dissector dissect some kind of payload

If I want to pop up a window when http dissector dissect some kind of payload,where can I write the gtk code ? ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe:

Re: [Wireshark-dev] Automatic test for a dissector DLL

H, Le lundi 13 décembre 2010 à 18:58 +0100, news.gmane.com a écrit : > Hi, > > I want to write a tester for my dissector. Since the procotol is complex it > is not sufficient, to load a captured file and verify visually the tree > output. I generated a set of synthetic capture files. Now the ide

Re: [Wireshark-dev] Automatic test for a dissector DLL

news.gmane.com writes: > How can I limit the output to one protocol level. As an example the TCP > level would be great (without IP, Ethernet, Frame)? Currently there is no way to do this, to my knowledge. ___ Sent via:

Re: [Wireshark-dev] [work in progress / stuck] improved dissection for VNC (correct hextile encoding, correct desegmentation)

Kaul writes: > Hi,Attached please find an incomplete, work-in-progress improved dissection of the VNC protocol. Hi Kaul, I think it would be better to open a bug report for this and submit the patches there. That way, the patches won't be forgotten. ___

[Wireshark-dev] Automatic test for a dissector DLL

Hi, I want to write a tester for my dissector. Since the procotol is complex it is not sufficient, to load a captured file and verify visually the tree output. I generated a set of synthetic capture files. Now the idea is to instruct tshark to parse the file using the dissector and compare the

[Wireshark-dev] buildbot failure in Wireshark (development) on Windows-7-x64

The Buildbot has detected a new failure of Windows-7-x64 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Windows-7-x64/builds/607 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: windows-7-x64 Build Reason: B

Re: [Wireshark-dev] Going forward on BSSGP bugreport #4880

I'm just wondering how relevant the check is, it's not likly to happen again? And supposedly the application would not work. Regards Anders -Original Message- From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Holger Freyther Sent: den 11