On Thu, Jan 3, 2019 at 5:36 PM hdv wrote:
>
> On 2-1-2019 18:30, Dario Lombardo wrote:
>
> You cannot trace your code using prints because they're handled by the
> caller (dumpcap). Have a look at the other extcaps for --debug and
> --debug-file options to see how it's solved there.
>
> I only se
On Jan 3, 2019, at 9:05 AM, Richard Sharpe wrote:
> I am sure that most people who work on the ieee80211 dissector will
> agree that it is a monster that needs taming.
>
> It is currently more than 37,000 lines long
IEEE Std 802.11-2016, section 9. "Frame formats" is about 658 pages;
IEEE Std
Hi folks,
I am sure that most people who work on the ieee80211 dissector will
agree that it is a monster that needs taming.
It is currently more than 37,000 lines long and a number of things
that have been done in it make it hard to split it in rational ways.
Perhaps the way that the Wi-Fi commu
On 2-1-2019 18:30, Dario Lombardo wrote:
You cannot trace your code using prints because they're handled by the
caller (dumpcap). Have a look at the other extcaps for --debug and
--debug-file options to see how it's solved there.
I only see g_warning/g_error/g_debug messages in the other extc
