Re: [Wireshark-dev] Why does the extcap stuff take so long to start up?

The problem is only when compiling with autotools. With cmake the bin extcap dir is clean and it doesn't affect startup time. Btw the check you added is wise and should be done anyway in case unwanted artifacts are there. The problem with extcaps is that androiddump is the only tool that

Re: [Wireshark-dev] Why does the extcap stuff take so long to start up?

On Mar 27, 2017, at 1:14 PM, Guy Harris wrote: > Currently, with that fix, I get results like > > $ time ./tshark -r /tmp/nothing.pcap > > real0m1.407s > user0m0.312s > sys 0m0.676s > > with the extcap directory in place and results like > > $ time ./tshark -r

Re: [Wireshark-dev] Why does the extcap stuff take so long to start up?

On Mar 26, 2017, at 11:30 PM, Michał Łabędzki wrote: > Could you check if any of extcap binaries generates that delay? A lot of the delay comes from extcap *non*-binaries; the code that scans the extcap directory tried running *everything* it finds there,

Re: [Wireshark-dev] RTP player - a suggestion

Hi Peter, >>> My proposal: >>> Add 'mixer' layer which will provide the following features to >>> improve usability: > > Your idea sounds good overall, but before you dive into it, can I > first suggest that a lot of the current problems are due to the use of > QCustomPlot for graphing the

Re: [Wireshark-dev] RTP player - a suggestion

Hi, >> I disagree. Right now, the GTK RTP player is the only one that I consider >> usable. By comparison, the Qt RTP player only barely works, and is unusable >> if you're dealing with more than one stream. If these changes can improve >> the Qt >version to be about as good as the GTK

Re: [Wireshark-dev] RTP player - a suggestion

Hi Erik and Jirka, Some comments for both of you (makes sense to reply to both together). Firstly, Erik, did you see my comments about the RTP player from a few months ago? (https://www.wireshark.org/lists/wireshark-dev/201612/msg00081.html) I didn't submit any of it as bug reports, but I could

Re: [Wireshark-dev] RTP player - a suggestion

On Mon, Mar 27, 2017 at 4:54 PM, Anders Broman wrote: > > > -Original Message- > From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-bounces@ > wireshark.org] On Behalf Of Peter Budny > Sent: den 27 mars 2017 16:48 > To: 'Developer support list for

Re: [Wireshark-dev] RTP player - a suggestion

-Original Message- From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Peter Budny Sent: den 27 mars 2017 16:48 To: 'Developer support list for Wireshark' Subject: Re: [Wireshark-dev] RTP player - a suggestion

Re: [Wireshark-dev] RTP player - a suggestion

Hi Anders, > -Original Message- > From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Anders Broman > Sent: Monday, March 27, 2017 4:12 AM > To: Developer support list for Wireshark > Subject: Re: [Wireshark-dev] RTP player - a suggestion >

Re: [Wireshark-dev] Ubuntu PPAs

-Original Message- From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Peter Wu Sent: den 14 mars 2017 17:33 To: Bálint Réczey Cc: Developer support list for Wireshark Subject: Re:

Re: [Wireshark-dev] Default snaplen in man page

Hi Martin, Yes, there is a bug on man (forget to update after last update... https://code.wireshark.org/review/2658 ) You can open a bug or push directly on fix. Cheers On Mon, Mar 27, 2017 at 9:46 AM, Martin Sehnoutka wrote: > Hello, > > I'm investigating why Wireshark

[Wireshark-dev] Default snaplen in man page

Hello, I'm investigating why Wireshark is dropping packets when capturing over loopback and I think the man page is wrong with the default snaplen. It says that the default size is 65535, but if I'm not mistaken the default size is set in capture_opts.c which leads to WTAP_MAX_PACKET_SIZE in

Re: [Wireshark-dev] Why does the extcap stuff take so long to start up?

Hello Guy, Could you check if any of extcap binaries generates that delay? (check one by one) On "my" Ubuntu 12.04: my_extcap[4] = {androiddump, randpktdump, udpdump, my custom extcap}; $ time ./run/tshark -D # returns 21 interfaces real0m0.188s user0m0.115s sys 0m0.061s