On Nov 23, 2020, at 7:09 AM, Timmy Brolin wrote:
> Reading up on it a bit, turns out there is no such thing as SIGTERM in
> Windows.
Correct.
> There seems to exist several alternative ways of doing it in Windows.
>
> Such as sending WM_QUIT or WM_CLOSE on the message queue,
This assumes
Hi Chris,
Le lun. 23 nov. 2020 à 20:38, Maynard, Christopher via Wireshark-dev <
wireshark-dev@wireshark.org> a écrit :
> > From: Wireshark-dev On Behalf Of
> Anders Broman via Wireshark-dev
> > Sent: Thursday, November 19, 2020 3:50 AM
> > To: wireshark-dev@wireshark.org
> > Cc: Anders Broman
> From: Wireshark-dev On Behalf Of Anders
> Broman via Wireshark-dev
> Sent: Thursday, November 19, 2020 3:50 AM
> To: wireshark-dev@wireshark.org
> Cc: Anders Broman
> Subject: [Wireshark-dev] Qt warning on Windows build.
>
> Hi,
> Currently there is one Warnimg produced for the Windows build
>Message: 1
>Date: Fri, 20 Nov 2020 17:43:33 -0800
>From: Guy Harris
>To: Developer support list for Wireshark
>Subject: Re: [Wireshark-dev] wireshark capture/filtering question
>Message-ID: <31e12e1e-224b-4223-af81-659e1b6bf...@sonic.net>
>Content-Type: text/plain; charset=us-ascii
>
>On
The signal handler is called when extcap is executed stand-alone, and killed
with Ctrl+C (SIGINT).
But the signal handler is not called when Wireshark executes the extcap.
I have not tried the code in unix. I have no unix machine around.
Reading up on it a bit, turns out there is no such thing
Indeed the used signal to terminate the extcap is SIGTERM.
Is your signal handler called? Did you run a debugger to see which signal
is interrupting your code?
Did you try your code on unix?
On Mon, Nov 23, 2020 at 10:31 AM Timmy Brolin wrote:
> I am writing a extcap plugin for Wireshark
I am writing a extcap plugin for Wireshark (Windows version). The documentation
on how Wireshark stops a extcap capture is a bit sketchy, but it seems it
simply terminates the extcap plugin.
If I run the extcap binary standalone, and stops it with Ctrl+C, everything
works as expected. The
