[Wireshark-dev] buildbot failure in Wireshark (development) on Ubuntu-9.10-x64

2010-04-14 Thread buildbot-no-reply
The Buildbot has detected a new failure of Ubuntu-9.10-x64 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Ubuntu-9.10-x64/builds/18 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: ubuntu-9.10-x64 Build Reaso

Re: [Wireshark-dev] Printing?

2010-04-14 Thread Ed Beroset
Shawn Mayer wrote: > Do I have to use something other than printf to print from Wireshark? I > have the console set to always open, but still am not seeing anything. It works just fine under Linux, so I assume you must be on a Windows machine. Try this: http://dslweb.nwnexus.com/~ast/dload/gui

Re: [Wireshark-dev] Printing?

2010-04-14 Thread Graham Bloice
On 14/04/2010 01:59, Shawn Mayer wrote: > Do I have to use something other than printf to print from Wireshark? I > have the console set to always open, but still am not seeing anything. > Thanks. > > > Run it under the debugger, much easier than printf. -- Regards, Graham Bloice _

[Wireshark-dev] buildbot failure in Wireshark (development) on Windows-XP-x86

2010-04-14 Thread buildbot-no-reply
The Buildbot has detected a new failure of Windows-XP-x86 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Windows-XP-x86/builds/27 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: windows-xp-x86 Build Reason:

Re: [Wireshark-dev] Printing?

2010-04-14 Thread Graham Bloice
On 14/04/2010 14:00, Shawn Mayer wrote: > On 14/04/2010 01:59, Shawn Mayer wrote: >> Do I have to use something other than printf to print from Wireshark? I >> have the console set to always open, but still am not seeing anything. >> Thanks. >> >> > Run it under the debugger, much easier than p

Re: [Wireshark-dev] Attempting new dissectors using ASN and asn2wrs under MSVC 2008E

2010-04-14 Thread Adrienne E. Siskind
Thanks, Anders. Both suggestions helped. Turns out that's not the only ASN construct in the SLE specs that asn2wrs doesn't like, so I'll be making a list of them as I progress. -- [snip - using foo example from wiki] > > The resulting compile fails for the asn2wrs-generated pac

Re: [Wireshark-dev] Printing?

2010-04-14 Thread Beth
printf worked fine for me on Windows. g_printf compiled fine but never printed anything. ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org

[Wireshark-dev] FW: Announcing "Ostinato" - packet generator and analyzer

2010-04-14 Thread Maynard, Chris
I saw this on another mailing list and thought it might be of interest to many people on this list as well, so I'm posting it here for the benefit of those who may not have seen it elsewhere. - Chris -Original Message- Ostinato Ostinato is an open sou

Re: [Wireshark-dev] FW: Announcing "Ostinato" - packet generator and analyzer

2010-04-14 Thread Jakub Zawadzki
On Wed, Apr 14, 2010 at 10:12:01AM -0400, Maynard, Chris wrote: > I saw this on another mailing list and thought it might be of interest to > many people on this list as well, > so I'm posting it here for the benefit of those who may not have seen it > elsewhere. I've already seen it on wireshar

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

2010-04-14 Thread buildbot-no-reply
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/34 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: windows-7-x64 Build Reason: Bu

[Wireshark-dev] buildbot failure in Wireshark (development) on Windows-XP-x86

2010-04-14 Thread buildbot-no-reply
The Buildbot has detected a new failure of Windows-XP-x86 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Windows-XP-x86/builds/29 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: windows-xp-x86 Build Reason:

Re: [Wireshark-dev] FW: Announcing "Ostinato" - packet generator and analyzer

2010-04-14 Thread Maynard, Chris
OK, but not everyone is subscribed to both lists so some developers might not have seen it. - Chris -Original Message- From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Jakub Zawadzki Sent: Wednesday, April 14, 2010 10:54 AM To: Developer

[Wireshark-dev] buildbot health?

2010-04-14 Thread Jeff Morriss
We've been getting a lot of "slave lost" failures on the Windows buildbots lately (I count 8 in 10 days on the Win32 bot). Anything wrong there? ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshar

Re: [Wireshark-dev] buildbot health?

2010-04-14 Thread Gerald Combs
Jeff Morriss wrote: > We've been getting a lot of "slave lost" failures on the Windows > buildbots lately (I count 8 in 10 days on the Win32 bot). Anything > wrong there? They're behind an oversubscribed DSL connection. We're hoping to get a higher speed link in the next few weeks. -- Join us

Re: [Wireshark-dev] Attempting new dissectors using ASN and asn2wrs under MSVC 2008E

2010-04-14 Thread Anders Broman
Adrienne E. Siskind skrev 2010-04-14 15:35: > Thanks, Anders. Both suggestions helped. > > Turns out that's not the only ASN construct in the SLE specs that > asn2wrs doesn't like, so I'll be making a list of them as I progress. > If you intend to commit this to wireshark when you are finished

Re: [Wireshark-dev] Printing?

2010-04-14 Thread Anders Broman
Hi, I use g_warning() or proto_add_text() Regards Anders Beth skrev 2010-04-14 16:10: printf worked fine for me on Windows. g_printf compiled fine but never printed anything. ___ Sent via:Wireshark-dev mailing list

[Wireshark-dev] buildbot failure in Wireshark (development) on OSX-10.5-x86

2010-04-14 Thread buildbot-no-reply
The Buildbot has detected a new failure of OSX-10.5-x86 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/OSX-10.5-x86/builds/33 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: osx-10.5-x86 Build Reason: Build

[Wireshark-dev] buildbot failure in Wireshark (development) on OSX-10.5-PowerPC

2010-04-14 Thread buildbot-no-reply
The Buildbot has detected a new failure of OSX-10.5-PowerPC on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/OSX-10.5-PowerPC/builds/30 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: osx-10.5-ppc Build Reason

[Wireshark-dev] buildbot failure in Wireshark (development) on Ubuntu-9.10-x64

2010-04-14 Thread buildbot-no-reply
The Buildbot has detected a new failure of Ubuntu-9.10-x64 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Ubuntu-9.10-x64/builds/23 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: ubuntu-9.10-x64 Build Reaso

[Wireshark-dev] Wrong link to Visual C++ 2008 Express Edition from online Win32 developer guide

2010-04-14 Thread Maynard, Chris
Now that Microsoft Visual Studio 2010 is out, the compiler download link from the Win32 online developer guide (http://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html) redirects you to 2010 instead of to 2008. It looks like the link should be updated to bring you here now: http://ww

[Wireshark-dev] Packet colorization

2010-04-14 Thread Ari Yoskovitz
Hi! I am writing a dissector for this protocol I am working with. I will just refer to it as "my protocol". I can't seem to find ways to control packet colorization programatically, from within the dissector's code (int contrast to changing it manually from Wireshark's menus). Two issues came up:

Re: [Wireshark-dev] Packet colorization

2010-04-14 Thread Guy Harris
On Apr 14, 2010, at 3:12 PM, Ari Yoskovitz wrote: > I am writing a dissector for this protocol I am working with. I will just > refer to it as "my protocol". > I can't seem to find ways to control packet colorization programatically, > from within the dissector's code (int contrast to changing

[Wireshark-dev] Getting data from pinfo

2010-04-14 Thread Shawn Mayer
Am I correct in thinking that packet_info *pinfo is a tree with all of the relevant data per packet? What function is used to access the data it contains? Thanks. Shawn NTMail K12 - the Mail Server for Education ___ Sent vi

Re: [Wireshark-dev] Getting data from pinfo

2010-04-14 Thread Guy Harris
On Apr 14, 2010, at 4:12 PM, Shawn Mayer wrote: > Am I correct in thinking that packet_info *pinfo is a tree with all of > the relevant data per packet? No. It's not a tree of any sort. > What function is used to access the data it contains? For what particular piece of data are you looking?

[Wireshark-dev] buildbot failure in Wireshark (development) on Windows-XP-x86

2010-04-14 Thread buildbot-no-reply
The Buildbot has detected a new failure of Windows-XP-x86 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Windows-XP-x86/builds/33 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: windows-xp-x86 Build Reason:

Re: [Wireshark-dev] Wireshark - rtp desegment

2010-04-14 Thread Richard van der Hoff
Hi Lajos, I've copied in the wireshark dev mailing list, as others may be able to help with your query. I think the problem is that you are calling rtp_add_address for each packet. The idea is that you call it once for an entire RTP conversation. Typically it is called by something like the SI

Re: [Wireshark-dev] Getting data from pinfo

2010-04-14 Thread Shawn Mayer
I'm trying to get the IPs from an aim_messaging packet to pass to my tap. What exactly is pinfo and what does it contain? Should I avoid using it? On 4/14/2010 7:21 PM, Guy Harris wrote: > On Apr 14, 2010, at 4:12 PM, Shawn Mayer wrote: > > >> Am I correct in thinking that packet_info *pinfo

Re: [Wireshark-dev] Getting data from pinfo

2010-04-14 Thread Guy Harris
On Apr 14, 2010, at 6:07 PM, Shawn Mayer wrote: > I'm trying to get the IPs from an aim_messaging packet to pass to my > tap. Presumably the AIM dissector is setting up the call to your tap. If so, it should put the IP addresses into a data structure and pass that to the tap as private data;

Re: [Wireshark-dev] Getting data from pinfo

2010-04-14 Thread Shawn Mayer
Yes I have the tap being called from the aim messaging part of the dissector, since its the only part of the AIM protocol I'm interested in. I have a struct created to put the IP and other data I'm interested into, I'm just not sure where I get the IP from. On 4/14/2010 9:28 PM, Guy Harris wrot

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

2010-04-14 Thread buildbot-no-reply
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/40 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: windows-7-x64 Build Reason: Bu

[Wireshark-dev] buildbot failure in Wireshark (development) on Windows-XP-x86

2010-04-14 Thread buildbot-no-reply
The Buildbot has detected a new failure of Windows-XP-x86 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Windows-XP-x86/builds/35 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: windows-xp-x86 Build Reason:

Re: [Wireshark-dev] Getting data from pinfo

2010-04-14 Thread Guy Harris
On Apr 14, 2010, at 6:32 PM, Shawn Mayer wrote: > Yes I have the tap being called from the aim messaging part of the > dissector, since its the only part of the AIM protocol I'm interested > in. I have a struct created to put the IP and other data I'm interested > into, I'm just not sure where

[Wireshark-dev] Boolean Field Registration Qurey

2010-04-14 Thread Tamás Regõs
Hello, I have a question regarding to register a boolean field, especially about the FIELDBASE value. In README.developer it says the general rules: static hf_register_info hf[] = { { &hf_PROTOABBREV_FIELDABBREV, { "FIELDNAME", "PROTOABBREV.FIELDAB