Wireshark-dev: [Wireshark-dev] How to see where exception occurs in Malformed packets

From: Remy Leone <remy.leone@xxxxxxxx>
Date: Fri, 03 Mar 2017 16:56:45 +0000
Hello,

I'm trying to debug a malformed packet.
I've increased the log level to the level of 252 as mention in the following link: (https://wiki.wireshark.org/Development/Tips).
I don't see anything helpful showing up in the stdout when I dissect the problematic frame.
Most of my logs are composed of those kind of messages:

17:54:44  Capture Dbg  read 16 ok indicator: P len: 3 msg: 15
17:54:44  Capture Dbg  sync_pipe_input_cb: new packets 15
17:54:44     Main Dbg  Callback: capture update continue
17:54:44          Dbg  FIX: capture_info_ui_update

How can I enable as much helpful information as possible to help me understand what went wrong during the dissection?

Best regards

Rémy