Re: [Wireshark-dev] [Wireshark-bugs] [Bug 8995] build fails if system python is version 3+

On 7/31/13 3:49 PM, bugzilla-dae...@wireshark.org wrote: > *Comment # 8 > on bug > 8995 from Guy > Harris * > > (In reply to comment #3 ) >> Created a

[Wireshark-dev] Recent changes in composite TVB (extra changes beside move)

Hi, I should've first commit this changes and later move composite stuff to another file, but I haven't thought. Sorry. Anyway, attaching diff with important changes. If anyone has some time to do review it'd be great. Thanks, Kuba. --- 9d519b5659aa8c0c4aa984bc6169909eb31be7d6_2.c2013-

Re: [Wireshark-dev] [Wireshark-commits] rev 50896: / /trunk/doc/: README.qt /trunk/epan/: prefs-int.h prefs.c prefs.h uat-int.h uat.h /trunk/ui/qt/: CMakeLists.txt Makefile.common QtShark.pro elided_l

On 7/30/13 1:00 PM, Joerg Mayer wrote: > On Tue, Jul 30, 2013 at 11:41:09AM -0700, Gerald Combs wrote: >> BTW, it looks like you can pull Makefile-style definitions into CMake. >> This would make maintenance easier everywhere, not just in ui/qt: >> >> https://github.com/berenm/xoreos/blob/a187e94ec

Re: [Wireshark-dev] The field called Command Sequence Number in the SMB2 dissector is actually the Message ID

while you are renaming the displayed name of this variable, the rest of the SMB2 dissector is using the term "sequence number" in many places. It's now confusing if source code comments talk about sequence numbers and use them in hash tables, while the dissection shows it as Message ID. To really w

Re: [Wireshark-dev] Problems building installer on Windows 8

On 31 July 2013 10:16, John OSullivan wrote: > Hi, > > ** ** > > I have downloaded the latest code for wireshark to build on a Windows 8 > (64 bit) machine. > > I am building an x86 version and can build all stages up to > > nmake –f Makefile.nmake packaging > > At this point it

Re: [Wireshark-dev] Problems building installer on Windows 8

than uninstallers Fatal error U1077: makensis.exe Any ideas why this step is failing? -- next part -- An HTML attachment was scrubbed... URL: <http://www.wireshark.org/lists/wireshark-dev/attachments/20130731/8c03efa0/ attachment.html> ---

Re: [Wireshark-dev] Wireshark trunk does not compile without HAVE_LIBGNUTLS

Sorry about that, fixed in r51067. On Wed, Jul 31, 2013 at 11:28 AM, Anders Broman wrote: > Index: epan/dissectors/packet-ssl-utils.h > > === > > --- epan/dissectors/packet-ssl-utils.h (revision 2107) > > +++ epan/dissectors/packet-

Re: [Wireshark-dev] Problems building installer on Windows 8

ing? -- next part -- An HTML attachment was scrubbed... URL: <http://www.wireshark.org/lists/wireshark-dev/attachments/20130731/8c03efa0/ attachment.html> -- Message: 8 Date: Wed, 31 Jul 2013 09:25:07 + From: Anders Broman To:

[Wireshark-dev] Wireshark trunk does not compile without HAVE_LIBGNUTLS

Index: epan/dissectors/packet-ssl-utils.h === --- epan/dissectors/packet-ssl-utils.h (revision 2107) +++ epan/dissectors/packet-ssl-utils.h (working copy) @@ -30,6 +30,7 @@ #include #include +#include #ifdef HAVE_LIBGNUTLS #incl

Re: [Wireshark-dev] Feeding the 802.15.4 Dissector

Hey Tomasz, thanks for the anwser. But my main question is how to write the bytes into the pipe so that Wireshark recognizes them as IEEE 802.15.4 packets, kinda like a structure that Wireshark is waiting for. I cannot just write the packet into the pipe, Wireshark gives me an error :S Thanks agai

Re: [Wireshark-dev] The field called Command Sequence Number in the SMB2 dissector is actually the Message ID

On 07/31/13 09:00, Richard Sharpe wrote: > Hi folks, > > This patch needs to be applied: Checked in r51066. ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe:

[Wireshark-dev] The field called Command Sequence Number in the SMB2 dissector is actually the Message ID

Hi folks, This patch needs to be applied: Index: epan/dissectors/packet-smb2.c === --- epan/dissectors/packet-smb2.c (revision 51065) +++ epan/dissectors/packet-smb2.c (working copy) @@ -7100,8 +7100,8 @@ proto_register_s

Re: [Wireshark-dev] Feeding the 802.15.4 Dissector

Thank You so much Guy and Tomasz, that was exactly what I was looking for. Best Regards, Rui Cumprimentos, Rui Pedro Caldeira On Wed, Jul 31, 2013 at 11:17 AM, Guy Harris wrote: > > On Jul 31, 2013, at 2:46 AM, Rui Pedro Caldeira > wrote: > > > Hey Tomasz, thanks for the anwser. But my main

Re: [Wireshark-dev] Feeding the 802.15.4 Dissector

On Jul 31, 2013, at 2:46 AM, Rui Pedro Caldeira wrote: > Hey Tomasz, thanks for the anwser. But my main question is how to write the > bytes into the pipe so that Wireshark recognizes them as IEEE 802.15.4 > packets, kinda like a structure that Wireshark is waiting for. I cannot just > write

Re: [Wireshark-dev] Feeding the 802.15.4 Dissector

Hey Tomasz, thanks for the anwser. But my main question is how to write the bytes into the pipe so that Wireshark recognizes them as IEEE 802.15.4 packets, kinda like a structure that Wireshark is waiting for. I cannot just write the packet into the pipe, Wireshark gives me an error :S Thanks agai

Re: [Wireshark-dev] Problems building installer on Windows 8

Hi, Have you set WIRESHARK_TARGET_PLATFORM=win32 And run .. \"vcvarsall.bat x86 Regards Anders From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of John OSullivan Sent: den 31 juli 2013 11:17 To: wireshark-dev@wireshark.org Subject: [Wireshark-dev] P

[Wireshark-dev] Problems building installer on Windows 8

Hi, I have downloaded the latest code for wireshark to build on a Windows 8 (64 bit) machine. I am building an x86 version and can build all stages up to nmake -f Makefile.nmake packaging At this point it fails with an error: Internal Compiler Error: Installers shell constants are differe