Re: [Wireshark-commits] rev 40312: /trunk/ /trunk/epan/dissectors/: packet-bt-dht.c packet-gopher.c packet-gsm_ipa.c packet-meta.c packet-mux27010.c packet-nfs.c packet-rdp.c packet-sametime.c packet-ua.c packet-xtp.c ...

["Maynard, Chris" <Christopher.Maynard () GTECH COM>]

> -----Original Message-----
> From: wireshark-commits-bounces () wireshark org [mailto:wireshark-
> commits-bounces () wireshark org] On Behalf Of cmaynard () wireshark org
> Sent: Wednesday, December 28, 2011 11:37 AM
> To: wireshark-commits () wireshark org
> Subject: [Wireshark-commits] rev 40312: /trunk/
> /trunk/epan/dissectors/: packet-bt-dht.c packet-gopher.c packet-
> gsm_ipa.c packet-meta.c packet-mux27010.c packet-nfs.c packet-rdp.c
> packet-sametime.c packet-ua.c packet-xtp.c ...
>
> http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=40312
>
> User: cmaynard
> Date: 2011/12/28 08:36 AM
>
> Log:
>  Fix memory leaks involving tvb_get_string[z]().
>
> Directory: /trunk/epan/dissectors/
>   Changes    Path                 Action
>   +5 -5      packet-bt-dht.c      Modified
>   +1 -0      packet-gopher.c      Modified
>   +1 -1      packet-gsm_ipa.c     Modified
>   +3 -0      packet-meta.c        Modified
>   +7 -5      packet-mux27010.c    Modified
>   +3 -0      packet-nfs.c         Modified
>   +6 -6      packet-rdp.c         Modified
>   +1 -1      packet-sametime.c    Modified
>   +4 -4      packet-ua.c          Modified
>   +1 -0      packet-xtp.c         Modified
>
>
> (1 file not shown)
> _______________________________________________________________________
> ____

I hadn't scheduled this (along with 40313) to be backported, but maybe they should be?  Also, what of Bill's recent 
work with tvbuff's?  I believe he fixed a lot of memory leaks there as well.

- Chris

-- 

CONFIDENTIALITY NOTICE: The information contained in this email message is intended only for use of the intended 
recipient. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, 
distribution or copying of this communication is strictly prohibited. If you have received this communication in error, 
please immediately delete it from your system and notify the sender by replying to this email.  Thank you.

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe