Re: Debugging Wireshark dissector plugins

[wsgd <wsgd () free fr>]

Perhaps, it is a particular packet that trigger the problem.
Try to split your capture file to find it.
Or use tshark.exe to see (inside the output) where it stops or loops.

I think printf should work (set "Preferences / Open a console window" to 
"Always").


Olivier


sean bzd a écrit :
> I asked a similar question before but got no response. Can someone 
> please provide some direction? 
>
> Problem:
> I have a custom dissector and works fine most of the time; but 
> sometimes, when I load the network capture containing packets (that 
> the dissector is supposed to understand), the Wireshark application 
> just hangs. The CPU consumption goes to 50% and stays there...it is as 
> if it is in a tight loop. I'm using version 1.2.2 but same happens 
> with different versions of wireshark; I know that the problem is in 
> the dissector because if I remove the dissector plugin, wireshark is 
> able to load the capture file. But i need some direction on how to 
> proceed forward. Can i put some printfs in the dissector or elsewhere? 
> Any other ideas?
>
> Thanks,
> Sean
> ------------------------------------------------------------------------
>
> ___________________________________________________________________________
> Sent via:    Wireshark-users mailing list <wireshark-users () wireshark org>
> Archives:    http://www.wireshark.org/lists/wireshark-users
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
>              mailto:wireshark-users-request () wireshark org?subject=unsubscribe

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