[Winpcap-users] Memory Management with pcap_next_ex()

[Gianluca Varenni]

No. Snaplen has nothing to do with the memory management of pcap_next_ex.

Have a nice day
GV

----- Original Message ----- 
From: "Gangadharan, Sandeep" <sandeep.gangadharan at hp.com>
To: <winpcap-users at winpcap.org>
Sent: Monday, August 18, 2008 8:18 PM
Subject: RE: [Winpcap-users] Memory Management with pcap_next_ex()


> Hi Slavy
>        Check the snaplen of pacp_open function is big enough!!
> Regards
> sandeep
>
> -----Original Message-----
> From: winpcap-users-bounces at winpcap.org 
> [mailto:winpcap-users-bounces at winpcap.org] On Behalf Of Stanislav Tsanev
> Sent: Tuesday, August 19, 2008 7:40 AM
> To: winpcap-users at winpcap.org
> Subject: [Winpcap-users] Memory Management with pcap_next_ex()
>
> I am using pcap_next_ex() to read packets from a capture file. Who is
> responsible for managing the memory that the two pointers I get back
> from the function call point to? Is that memory reused as is the case
> when I use a callback? If that's the case, how long is it guaranteed to
> persist? If not, how do I free it?
>
> I was looking for documentation on that but couldn't find anything.
>
> thank,
> slavy
>
> _______________________________________________
> Winpcap-users mailing list
> Winpcap-users at winpcap.org
> https://www.winpcap.org/mailman/listinfo/winpcap-users
>
> _______________________________________________
> Winpcap-users mailing list
> Winpcap-users at winpcap.org
> https://www.winpcap.org/mailman/listinfo/winpcap-users