Wireshark-dev: Re: [Wireshark-dev] Running a function only on first run
From: Anders Broman <anders.broman@xxxxxxxxxxxx>
Date: Wed, 7 Apr 2010 15:26:40 +0200
Hi,
Sorry
XXX:~/wireshark> grep -r PINFO_FD_VISITED *
epan/frame_data.h:#define PINFO_FD_VISITED(pinfo)   ((pinfo)->fd->flags.visited)

________________________________________
From: wireshark-dev-bounces@xxxxxxxxxxxxx [wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Anders Broman [anders.broman@xxxxxxxxxxxx]
Sent: Wednesday, April 07, 2010 3:24 PM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Running a function only on first run

Hi,
I don't think there is one...
/Anders
________________________________________
From: wireshark-dev-bounces@xxxxxxxxxxxxx [wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Jeremy O'Brien [obrien654j@xxxxxxxxx]
Sent: Wednesday, April 07, 2010 3:15 PM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Running a function only on first run

This is the file I found that contains the definition I need, but I
still do not see the PINFO_FD_VISITED macro you specified...

On Tue, Apr 6, 2010 at 16:36, Maynard, Chris
<Christopher.Maynard@xxxxxxxxx> wrote:
> epan/frame_data.h.
> - Chris
>
> -----Original Message-----
> From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Jeremy O'Brien
> Sent: Tuesday, April 06, 2010 1:43 PM
> To: Developer support list for Wireshark
> Subject: Re: [Wireshark-dev] Running a function only on first run
>
> On Tue, Apr 6, 2010 at 12:58, Graham Bloice <graham.bloice@xxxxxxxxxxxxx> wrote:
>> Try PINFO_FD_VISITED(pinfo) on the pinfo you have.  Visited gets set after
>> the first pass.
>
> I cannot find this macro. Where is it defined? It would be very nice
> to have since pinfo->fd->flags.visited is kind of cumbersome.
>
> CONFIDENTIALITY NOTICE: The contents of this email are confidential
> and for the exclusive use of the intended recipient. If you receive this
> email in error, please delete it from your system immediately and
> notify us either by email, telephone or fax. You should not copy,
> forward, or otherwise disclose the content of the email.
>
> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
> Archives:    http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>             mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
>
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe