Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-users: Re: [Wireshark-users] RTCP: Filtering SDES items in 'tshark'

From: Martin Thorpe <martinjasonthorpe@xxxxxxxxxxxxxx>
Date: Wed, 16 Nov 2011 18:18:02 +0000
Hi Guy

Thanks for your reply

You are correct my apologies I did indeed install Wireshark from the SVN - having installed the latest stable version it now works perfect! 

I'll pay more attention to the version I install next time :-)

Thanks 

Sent from my iPhone

On 16 Nov 2011, at 02:08, Guy Harris <guy@xxxxxxxxxxxx> wrote:

> 
> On Nov 15, 2011, at 4:52 PM, Martin Thorpe wrote:
> 
>> I've upgraded wireshark from 1.2 (CentOS 6 x64) to version 1.7.1 in order to use the command extension that Jaap kindly highlighted below; and now when I run the following trace I get the "Mysql protocol dissector: all fields should be little endian" bug:
> 
>    ...
> 
>> ** (process:31148): WARNING **: Dissector bug, protocol MySQL, in packet 377: proto.c:2508: failed assertion "hfinfo->type == FT_STRING || hfinfo->type == FT_STRINGZ"
> 
> That's not the "Mysql protocol dissector: all fields should be little endian", that's the "Mysql protocol dissector: adding a non-FT_STRING or non-FT_STRINGZ field with proto_tree_add_string() is an error" bug.  I just checked in a fix for at least one instance of that bug.
> 
>> This scrolls up the screen, there were no errors during the build compilation process?
> 
> Unfortunately, the build process doesn't catch all forms of incorrect code, so....
> 
>> 
>> Any help would be appreciated
> 
> There's no 1.7.1 release (the current development release is 1.7.0), so presumably "I've upgraded wireshark from 1.2 (CentOS 6 x64) to version 1.7.1" means "I built Wireshark from the Subversion trunk"; update to the current top-of-trunk and rebuild.
> 
> ___________________________________________________________________________
> Sent via:    Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
> Archives:    http://www.wireshark.org/lists/wireshark-users
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
>             mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe