Re: [Wireshark-dev] RPM for Wireshark 1.0.0 & above (RHEL 4)

2009-03-27 Thread Satish Chandra
Hi, You have create your own RPM of wireshark. Why I recommend this is because many a times RPM created on other Linux machines do not get installed. I have faced this problem as it starts complaining about missing libraries. If you have multiple Linux machines having the same copy of Linux on wh

[Wireshark-dev] buildbot failure in Wireshark (development) on Ubuntu-7.10-x86-64

2009-03-27 Thread buildbot-no-reply
The Buildbot has detected a new failure of Ubuntu-7.10-x86-64 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Ubuntu-7.10-x86-64/builds/830 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: ubuntu-7.10-x86 Buil

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

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

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

2009-03-27 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/2040 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: osx-10.5-x86 Build Reason: Bui

Re: [Wireshark-dev] [Wireshark-commits] rev 27872: /trunk/ /trunk/epan/dissectors/: packet-tcp.c /trunk/doc/: README.developer README.malloc /trunk/epan/: emem.c emem.h libwireshark.def

2009-03-27 Thread Guy Harris
On Mar 27, 2009, at 4:22 PM, Stephen Fisher wrote: > Can we work unicode (UTF-8) support into these new string functions? What does "Unicode (UTF-8) support" mean in this context? If a string passed as the initial value, a string passed to ep_strbuf_append(), a format string passed to ep_st

Re: [Wireshark-dev] [Wireshark-commits] rev 27872: /trunk/ /trunk/epan/dissectors/: packet-tcp.c /trunk/doc/: README.developer README.malloc /trunk/epan/: emem.c emem.h libwireshark.def

2009-03-27 Thread Stephen Fisher
Can we work unicode (UTF-8) support into these new string functions? It's something we've been meaning to get around to and I just figured this might be a good place to start. On Fri, Mar 27, 2009 at 11:05:46PM +, ger...@wireshark.org wrote: > http://anonsvn.wireshark.org/viewvc/viewvc.cgi?

[Wireshark-dev] String buffers added to emem.[ch]

2009-03-27 Thread Gerald Combs
I just checked in support for string buffers to emem.[ch], which are growable strings similar to GStrings. You can use them to do things like the following: emem_strbuf_t *strbuf; strbuf = ep_strbuf_new_label("Flags: "); ep_strbuf_printf_append(strbuf, "%s (%04x)", "lemons", 2); ep_strbuf_print

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

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

[Wireshark-dev] buildbot failure in Wireshark (development) on Ubuntu-7.10-x86-64

2009-03-27 Thread buildbot-no-reply
The Buildbot has detected a new failure of Ubuntu-7.10-x86-64 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Ubuntu-7.10-x86-64/builds/828 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: ubuntu-7.10-x86 Buil

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

2009-03-27 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/2037 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: osx-10.5-x86 Build Reason: Bui

Re: [Wireshark-dev] RPM for Wireshark 1.0.0 & above (RHEL 4)

2009-03-27 Thread Marc Milgram
On Fri, 27 Mar 2009 10:36 -0700, "vinayak kamath" wrote: Is there a website when i can get the link for rpm I obtain Red Hat Enterprise Linux updates through Red Hat Network http://rhn.redhat.com -Marc ___ Sent via:

Re: [Wireshark-dev] RPM for Wireshark 1.0.0 & above (RHEL 4)

2009-03-27 Thread vinayak kamath
Hi Marc, Is there a website when i can get the link for rpm -vinayak On Fri, Mar 27, 2009 at 8:44 AM, Marc Milgram < ether...@mmilgram.nospammail.net> wrote: > > On Thu, 26 Mar 2009 14:15 -0700, "vinayak kamath" > wrote: > > Where can i find the RPM for Wireshark 1.0.0 & above version > for

Re: [Wireshark-dev] RPM for Wireshark 1.0.0 & above (RHEL 4)

2009-03-27 Thread Marc Milgram
On Thu, 26 Mar 2009 14:15 -0700, "vinayak kamath" wrote: Where can i find the RPM for Wireshark 1.0.0 & above version for RHEL 4 platform. Wireshark 1.0.6 is available from Red Hat Enterprise Linux 4 Update 7. Marc Milgram

Re: [Wireshark-dev] dissector plugin help

2009-03-27 Thread Brian Oleksa
Philippe I have recompiled my plugin using "Microsoft Visual C++ 2008 Express Edition". I deployed it and it worked..!! It appears that the C RunTime Libraries where indeed the problem (version mismatch). Thanks for all your help. I should be good to go for now. Thanks again..!! Brian ph

Re: [Wireshark-dev] dissector plugin help

2009-03-27 Thread philippe alarcon
Hi Brian, We have not the same environment. On my station, I have generated WireShark 1.1.3, and I use "Microsoft Visual C++ 2008 Express Edition". In this environment, your plugin is running correctly. I remember that others have encountered problems for using a recent plugin with older version

Re: [Wireshark-dev] dissector plugin help

2009-03-27 Thread Brian Oleksa
Philippe I sent you an e-mail with some screen shots but it appears the screen shots were too big. So here is my outcome...maybe you will get the screenshots later. I still get the same results. I changed in the code where the ports file lives at to (c:/ports.txt). My ports.txt file is at the r