Re: Apply as Column not working correctly

[Jeff Morriss <jeff.morriss.ws () gmail com>]

Since I clearly wasn't answering/able to answer your question that's what I
was hoping for! :-)  Glad it worked out.

On Thu, Sep 29, 2016 at 5:51 PM, Paul Offord <Paul.Offord () advance7 com>
wrote:

> Yep – it was my fault.  I’ve fixed it.  Sorry to mess you around but your
> question did push me to the answer – so for me it was worthwhile.
>
>
>
> *From:* wireshark-dev-bounces () wireshark org [mailto:wireshark-dev-bounces@
> wireshark.org] *On Behalf Of *Paul Offord
> *Sent:* 29 September 2016 22:34
>
> *To:* Developer support list for Wireshark <wireshark-dev () wireshark org>
> *Subject:* Re: [Wireshark-dev] Apply as Column not working correctly
>
>
>
> Hi Jeff.  Scrap that.  My dissector break point was after an if statement
> that fails.  I think I have a logic problem in the transum dissector.  I’ll
> work on it.
>
>
>
> *From:* Paul Offord
> *Sent:* 29 September 2016 20:49
> *To:* 'Developer support list for Wireshark' <wireshark-dev () wireshark org>
> *Subject:* RE: [Wireshark-dev] Apply as Column not working correctly
>
>
>
> Hi Jeff, Yes that’s what I’m saying.
>
>
>
> *From:* wireshark-dev-bounces () wireshark org [mailto:wireshark-dev-bounces@
> wireshark.org <wireshark-dev-bounces () wireshark org>] *On Behalf Of *Jeff
> Morriss
> *Sent:* 29 September 2016 20:43
> *To:* Developer support list for Wireshark <wireshark-dev () wireshark org>
> *Subject:* Re: [Wireshark-dev] Apply as Column not working correctly
>
>
>
>
>
>
>
> On Thu, Sep 29, 2016 at 3:21 AM, Paul Offord <Paul.Offord () advance7 com>
> wrote:
>
> Hi,
>
>
>
> I’m debugging a problem with the transum dissector.  Repro steps are:
>
>
>
> ·        Right click on a TRANSUM RTE Data value such as APDU Rsp Time
> and choose Apply as Column
>
> ·        The column is added with the correct heading
>
> ·        If I look at the Column preferences I see the APDU Rsp Time
> column with a type of Custom and the correct field name of transum.art
>
> ·        I get a single callback through my dissector with
> PINFO_FD_VISITED(pinfo) == TRUE for frame 1 which is the frame I am
> displaying
>
> ·        None of my other callbacks are called
>
> Are you saying your dissector isn't called again for any other frames?
>
>
>
> ·        The APDU Rsp Time for frame 1 shows correctly in the column
>
> ·        No other APDU Rsp Time values appear in the packet list even
> though the tree is correctly constructed in the packet detail area
>
> So this means that if you click on, say, frame 2 (so you can see the
> packet detail area) the column is still not filled in?  Does your dissector
> get called when you click on the frame (it should be called--with 'tree'
> set).
>
>
> ______________________________________________________________________
>
> This message contains confidential information and is intended only for
> the individual named. If you are not the named addressee you should not
> disseminate, distribute or copy this e-mail. Please notify the sender
> immediately by e-mail if you have received this e-mail by mistake and
> delete this e-mail from your system.
>
> Any views or opinions expressed are solely those of the author and do not
> necessarily represent those of Advance Seven Ltd. E-mail transmission
> cannot be guaranteed to be secure or error-free as information could be
> intercepted, corrupted, lost, destroyed, arrive late or incomplete, or
> contain viruses. The sender therefore does not accept liability for any
> errors or omissions in the contents of this message, which arise as a
> result of e-mail transmission.
>
> Advance Seven Ltd. Registered in England & Wales numbered 2373877 at
> Endeavour House, Coopers End Lane, Stansted, Essex CM24 1SJ
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> ______________________________________________________________________
>
> ______________________________________________________________________
>
> This message contains confidential information and is intended only for
> the individual named. If you are not the named addressee you should not
> disseminate, distribute or copy this e-mail. Please notify the sender
> immediately by e-mail if you have received this e-mail by mistake and
> delete this e-mail from your system.
>
> Any views or opinions expressed are solely those of the author and do not
> necessarily represent those of Advance Seven Ltd. E-mail transmission
> cannot be guaranteed to be secure or error-free as information could be
> intercepted, corrupted, lost, destroyed, arrive late or incomplete, or
> contain viruses. The sender therefore does not accept liability for any
> errors or omissions in the contents of this message, which arise as a
> result of e-mail transmission.
>
> Advance Seven Ltd. Registered in England & Wales numbered 2373877 at
> Endeavour House, Coopers End Lane, Stansted, Essex CM24 1SJ
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> ______________________________________________________________________
>
> ____________________________________________________________
> _______________
> 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
___________________________________________________________________________
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