Re: [Wireshark-dev] Do we require lua version 5.1 for the lua plugin?

For practical reasons I removed lua 5.0.x support when I migrated wslua into epan. I thought I had modified the autogen stuff to reflect this. I think we should look for lua_getfield() to verify if we are using the right version. Luis On Tue, Apr 29, 2008 at 7:45 AM, Joerg Mayer [EMAIL

[Wireshark-dev] g_ascii_strcasecmp.c and friends

Hi, I started to remove code for g_ascii_strcasecmp and friends what remains is to remove stuff for it from configure files (which I not sure how to do) and Delete the files g_ascii_strcasecmp.c and friends. Regards Anders ___ Wireshark-dev mailing list

[Wireshark-dev] RTP Player annoyance

Gentle developers, I believe the new RTP Player placement has been discussed in the mailing list in the past. I'm not sure anyone has noticed, but the ability to type in the selection list on the left hand side is quite a nice feature. However, I can no longer type 'r' t' 'p' and go

Re: [Wireshark-dev] New Wireshark welcome page!

What is special about March 1st and June 14th? The welcome page will display a different welcome message from the message The World's Most Popular Network Protocol Analyzer on these two dates. Just curious. This got me very curious as well... so I did a bit of digging around and I finally

Re: [Wireshark-dev] Requiring GTK+ 2.4 or later

Guy Harris wrote: At least at one point, I seem to remember reading that the GtkTreeView was changed in GTK+ 2.4 to deal with a performance issue. A little searching indicated that this was the addition of a fixed height option, so it didn't have to calculate the height of every single

Re: [Wireshark-dev] Communication between Dissectors

Hi Barry, can /* Get reported length of buffer */ extern guint tvb_reported_length(tvbuff_t*); from tvbuff.h give you the information you need? HTH, Martin On 4/28/08, Barry Constantine [EMAIL PROTECTED] wrote: Hello All, I am not a developer per se, but wrote simple dissector

Re: [Wireshark-dev] SMTP : Copying Data into a file

Hi Julien, I have to copy all the data transferred into a mail (SMTP) into a file. I don't think I have to implement a new dissector because SMTP one already exist, no? Right. So I think I have to complete the existing one and add a method to create a file and copy the data in. Am I in

[Wireshark-dev] How to capture all IP fragments?

In Wireshark, if I want to capture UDP traffic on a specific port (say port 5 for purposes of this discussion), I can easily set a capture filter as udp port 5, and I get all the traffic I'm interested in, including all IP fragments. However, I have written my own pcap-based capturing

Re: [Wireshark-dev] RTP Player annoyance

Hi, The preference has already been moved into the statistics page, so it shouldn't conflict anymore. Thanx, Jaap Peter Fuller wrote: Gentle developers, I believe the new RTP Player placement has been discussed in the mailing list in the past. I'm not sure anyone has noticed, but

[Wireshark-dev] Should we also require GLib 2.4 or later?

GTK+ 2.4 requires GLib 2.4, so if we're building with GTK+, that requires GLib 2.4 or later. One could, I guess, build everything *but* Wireshark with an earlier version of GLib, but requiring 2.2 or later means that, for example, we wouldn't have to check for g_ascii_strtoull(), as that first

Re: [Wireshark-dev] RTP Player annoyance

Hello Peter, This might be related to a known issue: http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2325 Hope this helps! Abhik. On Mon, Apr 28, 2008 at 12:54 AM, Peter Fuller [EMAIL PROTECTED] wrote: Gentle developers, I believe the new RTP Player placement has been discussed in

Re: [Wireshark-dev] g_ascii_strcasecmp.c and friends

Anders Broman wrote: I started to remove code for g_ascii_strcasecmp and friends what remains is to remove stuff for it from configure files (which I not sure how to do) and Delete the files g_ascii_strcasecmp.c and friends. I've checked in a change to do that (and to remove an

Re: [Wireshark-dev] How to capture all IP fragments?

On Apr 29, 2008, at 9:48 AM, Maynard, Chris wrote: In Wireshark, if I want to capture UDP traffic on a specific port (say port 5 for purposes of this discussion), I can easily set a capture filter as udp port 5, and I get all the traffic I'm interested in, including all IP

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

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

Re: [Wireshark-dev] Should we also require GLib 2.4 or later?

On Tue, Apr 29, 2008 at 10:52:16AM -0700, Guy Harris wrote: GTK+ 2.4 requires GLib 2.4, so if we're building with GTK+, that requires GLib 2.4 or later. One could, I guess, build everything *but* Wireshark with an earlier version of GLib, but requiring 2.2 or later means that, for