Re: [Wireshark-dev] How to get calling dissector

Thanks a lot Roland. Now that I know what to look for packet-sip.c gives a nice example. Cheers Uli Am 29.01.18 um 18:03 schrieb Roland Knall: > Short answer: packet_info->layers should get you the list of protocols called > before yours. If you iterate, you should > see the other protocols

Re: [Wireshark-dev] error occurred WSLDFLAG_VALID0 - Failed

Ignore it, it's a test for a flag that's not supported by MSVC, so as it fails it won't be used. The flag has actually been removed for MSVC in the current master branch. On 29 January 2018 at 08:05, Nilesh Bhadule wrote: > > > hi, > > While doing Custom plugin Cmake generation

[Wireshark-dev] error occurred WSLDFLAG_VALID0 - Failed

hi, While doing Custom plugin Cmake generation step following error occurred WSLDFLAG_VALID0 - Failed, -- Performing Test CXX_w34295w34189wd4200VALID -- Performing Test CXX_w34295w34189wd4200VALID - Success statuscheck linker flag - test linker flags: -Wl,--as-needed -- Performing Test

Re: [Wireshark-dev] One quick question

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

Re: [Wireshark-dev] One quick question

Hi Krishnamurthy, Wireshark uses an executable called dumpcap to perform the actual capture. You can use dumpcap directly from the command line, and as dumpcap doesn’t build the structures that Wireshark builds you won’t have a memory problem. You can then view the resulting pcapng file with

Re: [Wireshark-dev] PLUGINS: Wireshark source code repository path

Yes, it is correct, as stated in the developer page: https://www.wireshark.org/develop.html However, the master branch of a project is very likely not the be the stable one. At least this is the truth for wireshark. If you want some stable branch, just run git remote show origin have a look at

[Wireshark-dev] PLUGINS: Wireshark source code repository path

Hi, I have cloned Wireshark source code from https://code.wireshark.org/review/wireshark and master branch. Is this the correct/stable Wireshark source code path? Thanks, Nilesh ___ Sent via:Wireshark-dev mailing list

Re: [Wireshark-dev] PLUGINS: Wireshark source code repository path

On 29 January 2018 at 11:45, Nilesh Bhadule wrote: > Hi, > > > > I have cloned Wireshark source code from > *https://code.wireshark.org/review/wireshark > *and master branch. > > > > Is this the correct/stable Wireshark source code

[Wireshark-dev] Luacov with Wireshark Lua dissector plugin

Hi, I would like to see the code coverage when I run tshark for a packet capture with a Lua dissector plugin. The command used is as follows: $ tshark -r input.pcap -X lua_script:dissector.lua I came across the following StackOverflow post, but, it doesn't give much details:

[Wireshark-dev] How to get calling dissector

Hi all, TL,DR: How does a dissector know which dissector called it? Long version: I’m currently implementing a dissector for „Session Multiplex Protocol“ (SMP) [1] requested in bug 14110 [2]. The Tabular Data Stream (TDS; MS SQL Server) protocol depends on SMP when using the MARS feature [3].

Re: [Wireshark-dev] How to get calling dissector

Short answer: packet_info->layers should get you the list of protocols called before yours. If you iterate, you should see the other protocols before yours. In packet.c:754 you see the code adding to the list. Not sure though, how stable that interface is. It is pretty in-depth for span, so you