Re: How to see where exception occurs in Malformed packets

[Remy Leone <remy.leone () inria fr>]

Hello

Le sam. 4 mars 2017 à 00:00, Jaap Keuter <jaap.keuter () xs4all nl> a écrit :

> 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

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe