is what I have implemented here:
https://gitlab.com/wireshark/wireshark/-/merge_requests/2063
Regards,
Timmy Brolin
From: Wireshark-dev On Behalf Of Timmy
Brolin
Sent: den 24 november 2020 11:07
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] How to properly finalize
> Windows Console applications have a handler to respond to console events, the
> default handler simply exits the process. Sending the console events is a
> little tricky, but there are workarounds, see here:
>
Windows Console applications have a handler to respond to console events,
the default handler simply exits the process. Sending the console events
is a little tricky, but there are workarounds, see here:
https://blog.codetitans.pl/post/sending-ctrl-c-signal-to-another-application-on-windows
.
> > 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 that the program you're trying to tell to terminate *has* a
> message queue to which it pays attention.
>
> Extcap programs are
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
Lombardo
Sent: den 23 november 2020 14:31
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] How to properly finalize capture in a Wireshark
extcap plugin?
Indeed the used signal to terminate the extcap is SIGTERM.
Is your signal handler called? Did you run a debugger to see
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
