is there a way to identify problematic code??

asked 2018-09-10 15:21:30 +0000

this post is marked as community wiki

This post is a wiki. Anyone with karma >750 is welcome to improve it.


I have added new messages to existing plugin code. When I go through the collected file, it is getting hung when I reach near to my message.

Is there any way to figure out reason for getting hung when cursor goes near to newly added packet code.

Is there anyway to debug wireshark plugin code by opening existing log file??

Thanks in advance

edit retag flag offensive close merge delete


Can you clarify the following:

  • Are you modifying a C dissector or a Lua one?
  • If a C dissector, have you tried attaching a debugger?
grahamb gravatar imagegrahamb ( 2018-09-10 15:30:39 +0000 )edit


yes, i am modifying a existing add on plugin C dissector. i have tried both attach/bring up wireshark using gdb, in both cases control was not reaching to the break point. in GUI window, whenever i go near to the requried packet in the captured log as i said GUI hungs but process ( wireshark status shows as Rl+ ).

Kuru4634 gravatar imageKuru4634 ( 2018-09-11 06:15:58 +0000 )edit