Hi,
Glib logging won't help you much, as in, malformed packet dissection isn't a
problem in the underlying infrastructure of the program (which would cause said
log messages to be generated), but a exception caught by the dissection engine
itself. The common way to get forward is to retrieve the source code for the
dissector the malformation is detected in and find the lines of code on which
this exception is raised.
How can I do this as efficiently as possible? I could do a bunch of printf but I was wondering if wireshark could help me find the exect lines at which the error occurs.
Best regards
Rémy