Re: [Wireshark-dev] Help compile a custom extension to lte

This was spot on. Thank you Pascal.And, yes, this needs to go into the developers guide. If possible, and not already done, i'd be happy to add this and a couple of minor edits. Regards. On Wed, Feb 17, 2016 at 5:23 PM, Graham Bloice wrote: On 17 February

Re: [Wireshark-dev] Help compile a custom extension to lte

On 17 February 2016 at 20:50, Pascal Quantin wrote: > Hi, > > 2016-02-17 20:49 GMT+01:00 Born In : > >> I am trying to add a custom extension to couple of LTE messages so I can >> see them in wireshark. >> Since I will be using wireshark exclusively

Re: [Wireshark-dev] androiddump no longer built with nmake -> packaging fails

Hi Anders, 2016-02-17 16:32 GMT+01:00 Anders Broman : > Hi, > > The files in the extcap folder are no longer built with nmake... > Should be fixed with https://code.wireshark.org/review/#/c/13986/1 Cheers, Pascal.

Re: [Wireshark-dev] Bit for starting / stopping / new Capture

Thanks Pascal – I always wondered when code appeared in a release. From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Pascal Quantin Sent: 17 February 2016 18:53 To: Developer support list for Wireshark Subject: Re:

Re: [Wireshark-dev] Help compile a custom extension to lte

Hi, 2016-02-17 20:49 GMT+01:00 Born In : > I am trying to add a custom extension to couple of LTE messages so I can > see them in wireshark. > Since I will be using wireshark exclusively in windows, I figured doing a > native win64 build will be the best way to proceed. >

[Wireshark-dev] Help compile a custom extension to lte

I am trying to add a custom extension to couple of LTE messages so I can see them in wireshark. Since I will be using wireshark exclusively in windows, I figured doing a native win64 build will be the best way to proceed. Accordingly, I followed the build environment setup process a

Re: [Wireshark-dev] Bit for starting / stopping / new Capture

2016-02-17 19:38 GMT+01:00 Paul Offord : > There’s an enhancement to plugin_if that doesn’t address your needs > directly but may give you enough functionality. It’s a function called > plugin_if_get_ws_info. You can call it from within a dissector and it > populates

Re: [Wireshark-dev] Bit for starting / stopping / new Capture

There’s an enhancement to plugin_if that doesn’t address your needs directly but may give you enough functionality. It’s a function called plugin_if_get_ws_info. You can call it from within a dissector and it populates the following structure: typedef struct _ws_info_t { gboolean

Re: [Wireshark-dev] Bit for starting / stopping / new Capture

On Feb 17, 2016, at 7:16 AM, "FIXED-TERM Scholz Tobias (DC-IA/EAI)" wrote: I made some recherché, but couldn’t find any information to this topic. Is there a possibility to know (special bit for example), whe ther the user stopped, started the

Re: [Wireshark-dev] Bit for starting / stopping / new Capture

Hey Pascal, I finally could solve it with your mentioned function “register_cleanup_routine()” ! :D Thanks a lot! Von: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] Im Auftrag von Pascal Quantin Gesendet: Mittwoch, 17. Februar 2016 16:45 An: Developer

Re: [Wireshark-dev] Bit for starting / stopping / new Capture

2016-02-17 16:38 GMT+01:00 FIXED-TERM Scholz Tobias (DC-IA/EAI) < fixed-term.tobias.sch...@boschrexroth.de>: > Hi Pascal, > > > > thanks for your answer. I don’t get exactly the meaning of this routine > functionality, but I think it is not what I’m searching for. > > > > For my dissector I need

Re: [Wireshark-dev] androiddump no longer built with nmake -> packaging fails

On 17 February 2016 at 15:32, Anders Broman wrote: > Hi, > > The files in the extcap folder are no longer built with nmake... > > Regards > > Anders > All part of the plan to get you to move to CMake :-) -- Graham Bloice

Re: [Wireshark-dev] Bit for starting / stopping / new Capture

Hi Pascal, thanks for your answer. I don’t get exactly the meaning of this routine functionality, but I think it is not what I’m searching for. For my dissector I need a special bit or value as a trigger, which says, that e.g. the capture has stopped or starts new. E.g.: capture isn’t

[Wireshark-dev] androiddump no longer built with nmake -> packaging fails

Hi, The files in the extcap folder are no longer built with nmake... Regards Anders ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev

Re: [Wireshark-dev] Bit for starting / stopping / new Capture

Hi Tobias, 2016-02-17 16:16 GMT+01:00 FIXED-TERM Scholz Tobias (DC-IA/EAI) < fixed-term.tobias.sch...@boschrexroth.de>: > Hey, > > I made some recherché, but couldn’t find any information to this topic. Is > there a possibility to know (special bit for example), whether the user > stopped,

[Wireshark-dev] Bit for starting / stopping / new Capture

Hey, I made some recherché, but couldn't find any information to this topic. Is there a possibility to know (special bit for example), whether the user stopped, started the capture or opened Wireshark new? That would be a great help for my dissector. Thanks in advance! T. Scholz

Re: [Wireshark-dev] pre-commit ImportError

When you try to push to gerrit it should generate a change id that you can edit into your commit message. ___ Sent via:Wireshark-dev mailing list Archives:

Re: [Wireshark-dev] pre-commit ImportError

On 17 February 2016 at 09:17, João Valverde < joao.valve...@tecnico.ulisboa.pt> wrote: > On 17-02-2016 09:07, POZUELO Gloria (BCS/PSD) wrote: > >> Using git bash and typing python shows me the following message: >> "cygheap base mismatch detected. This problem is probably due to using >>

Re: [Wireshark-dev] pre-commit ImportError

On 17-02-2016 09:07, POZUELO Gloria (BCS/PSD) wrote: Using git bash and typing python shows me the following message: "cygheap base mismatch detected. This problem is probably due to using incompatible versions of the Cygwin DLL." I'm no Windows expert but I think that means Cygwin python

Re: [Wireshark-dev] pre-commit ImportError

Using git bash and typing python shows me the following message: "cygheap base mismatch detected. This problem is probably due to using incompatible versions of the Cygwin DLL." I'm going to try the solution that it tells me... Thank you very much! -Original Message- From:

Re: [Wireshark-dev] pre-commit ImportError

The pre-commit dependency on python is a recent change. That ImportError is a python initialization error. Can you run python using "Git Bash"? On 17-02-2016 08:14, POZUELO Gloria (BCS/PSD) wrote: Ok, I've just tried to commit the changes only with the commit-msg hook and the Change-Id was

Re: [Wireshark-dev] pre-commit ImportError

Ok, I've just tried to commit the changes only with the commit-msg hook and the Change-Id was generated properly...I don't know what happen to the pre-commit hook, I'll keep on investigation what's going on... -Original Message- From: wireshark-dev-boun...@wireshark.org

Re: [Wireshark-dev] pre-commit ImportError

On 17-02-2016 07:48, POZUELO Gloria (BCS/PSD) wrote: Hello, I’d like to ask you about a problem with the pre-commit hook. It turns out that when I try to commit my changes it shows me a message that says: “ImportError: No module named site”, but when I delete the pre-commit hook it allows me

Re: [Wireshark-dev] pre-commit ImportError

Hello Pascal, Thank you for your quick answer. The thing is that Python seems to be working correctly, since when I type python in the terminal it shows me the python version and it enters in the python console mode, so I guess that something is happening with the pre-commit hook… From: