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

Wireshark-dev: Re: [Wireshark-dev] does packet-rtpproxy.c really lacks a "{" ?

From: Toralf Förster <toralf.foerster@xxxxxx>
Date: Mon, 16 Dec 2013 11:19:29 +0100
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

FWIW - I run into this problem last night - but was too tired to send
out the email.

Today I "enhanced"the email by the diff - ignoring, that I made a "svn
update" in the mean while. Nevertheless - the problem occurred last
night - I'm wondering why.


On 12/16/2013 10:57 AM, Toralf Förster wrote:
> W/o this diff to the tree :
> 
> tfoerste@n22 ~/devel/wireshark $ svn diff Index:
> epan/dissectors/packet-rtpproxy.c 
> ===================================================================
>
> 
- --- epan/dissectors/packet-rtpproxy.c   (revision 54138)
> +++ epan/dissectors/packet-rtpproxy.c   (working copy) @@ -290,7
> +290,7 @@ } else{ ti = proto_tree_add_item(rtpproxy_tree, 
> hf_rtpproxy_tag, tvb, begin, new_offset - begin, ENC_ASCII |
> ENC_NA); -               if ((guint)new_offset == begin){ +
> if ((guint) new_offset == begin) { proto_item_append_text(ti,
> "<skipped>"); /* A very first Offer/Update command */ 
> PROTO_ITEM_SET_GENERATED(ti); }
> 
> 
> I can't compile wireshark.
> 
> Just a local problem or was a file checked-in w/o any compile
> checks ?
> 
> 

- -- 
MfG/Sincerely
Toralf Förster
pgp finger print:1A37 6F99 4A9D 026F 13E2 4DCF C4EA CDDE 0076 E94E
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iF4EAREIAAYFAlKu07EACgkQxOrN3gB26U6kdQD+MeQlj8qedUmAkFSWvRQc1OW/
9IJOAstwq3bHvFYFWZ8A/jhwLfh01p5EOxDuxiT+TY/UXE4acN2VU7TU0xpgtUNu
=Rh29
-----END PGP SIGNATURE-----