[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wireshark-dev
Subject:    Re: [Wireshark-dev] One quick question
From:       Krishnamurthy Mayya <krishnamurthymayya () gmail ! com>
Date:       2018-01-29 9:32:41
Message-ID: CA+cY5y6o_yr1-qWv-O0Y7Luo_QR2bUJP5ZFMrEdqUv8AB2yMbw () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Okay.
So, If I am sending continuos stream of data at the line rate(1gb/s) and if
I am using wireshark to capture the content, it will crash after sometime
due to memory exhaustion. Is there any way to bypass this ? (Any free
function/some other work around)
Any suggestion from your side would be extremely helpful. Thanks in advcane

Regards,
Krishnamurthy mayya


On Mon, Jan 8, 2018 at 11:05 PM, Guy Harris <guy@alum.mit.edu> wrote:

> On Jan 8, 2018, at 5:29 AM, Krishnamurthy Mayya <
> krishnamurthymayya@gmail.com> wrote:
>
> > epan_get_frame_ts
> >
> > Like the above function, is there any utility function in wireshark
> which fress the memory allocated for the given frame_num ?
>
> Are you assuming that epan_get_frame_ts() returns a pointer to a
> freshly-allocated structure that must be freed when the caller no longer
> needs it?
>
> If so, no, it doesn't.  You do not need to free the structure.
> ____________________________________________________________
> _______________
> Sent via:    Wireshark-dev mailing list <wireshark-dev@wireshark.org>
> Archives:    https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>              mailto:wireshark-dev-request@wireshark.org?subject=
> unsubscribe

[Attachment #5 (text/html)]

<div dir="ltr">Okay.<div>So, If I am sending continuos stream of data at the line \
rate(1gb/s) and if I am using wireshark to capture the content, it will crash after \
sometime</div><div>due to memory exhaustion. Is there any way to bypass this ? (Any \
free function/some other work around)</div><div>Any suggestion from your side would \
be extremely helpful. Thanks in \
advcane</div><div><br></div><div>Regards,</div><div>Krishnamurthy \
mayya</div><div><br></div></div><div class="gmail_extra"><br><div \
class="gmail_quote">On Mon, Jan 8, 2018 at 11:05 PM, Guy Harris <span \
dir="ltr">&lt;<a href="mailto:guy@alum.mit.edu" \
target="_blank">guy@alum.mit.edu</a>&gt;</span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><span class="">On Jan 8, 2018, at 5:29 AM, Krishnamurthy \
Mayya &lt;<a href="mailto:krishnamurthymayya@gmail.com">krishnamurthymayya@gmail.com</a>&gt; \
wrote:<br> <br>
&gt; epan_get_frame_ts<br>
&gt;<br>
&gt; Like the above function, is there any utility function in wireshark which fress \
the memory allocated for the given frame_num ?<br> <br>
</span>Are you assuming that epan_get_frame_ts() returns a pointer to a \
freshly-allocated structure that must be freed when the caller no longer needs \
it?<br> <br>
If so, no, it doesn&#39;t.   You do not need to free the structure.<br>
______________________________<wbr>______________________________<wbr>_______________<br>
 Sent via:      Wireshark-dev mailing list &lt;<a \
                href="mailto:wireshark-dev@wireshark.org">wireshark-dev@wireshark.org</a>&gt;<br>
                
Archives:      <a href="https://www.wireshark.org/lists/wireshark-dev" \
rel="noreferrer" target="_blank">https://www.wireshark.org/<wbr>lists/wireshark-dev</a><br>
                
Unsubscribe: <a href="https://www.wireshark.org/mailman/options/wireshark-dev" \
rel="noreferrer" target="_blank">https://www.wireshark.org/<wbr>mailman/options/wireshark-dev</a><br>
  mailto:<a href="mailto:wireshark-dev-request@wireshark.org">wireshark-dev-request@<wbr>wireshark.org</a>?subject=<wbr>unsubscribe</blockquote></div><br></div>



[Attachment #6 (text/plain)]

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

[prev in list] [next in list] [prev in thread] [next in thread]