This is a static archive of our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

How to debug tshark with exception offset

0

When I debug my version of tshark, warnings showed as below.I want to find the line of code where warnings come out, and wonder know how to do?

** (tshark.exe:22940): WARNING **: Dissector bug, protocol HTTP, in packet 64084
   : STATUS_ACCESS_VIOLATION: dissector accessed an invalid memory address
   140790
** (tshark.exe:22940): WARNING **: Dissector bug, protocol HTTP, in packet 14106
   3: STATUS_ACCESS_VIOLATION: dissector accessed an invalid memory address
   149454
** (tshark.exe:22940): WARNING **: Dissector bug, protocol HTTP, in packet 14957
   7: STATUS_ACCESS_VIOLATION: dissector accessed an invalid memory address
   159059

I just kown where to print the warning message, and I want to know where the bug is, how to do?

asked 01 Dec '13, 23:38

metamatrix's gravatar image

metamatrix
56161619
accept rate: 100%

edited 02 Dec '13, 09:52

Bill%20Meier's gravatar image

Bill Meier ♦♦
3.2k1850


One Answer:

0

You can use one of the usual suspects for debugging an exe on Windows, Visual Studio or WinDbg. Using the debugger of choice, start debugging tshark.exe in the wireshark-gtk directory of your build environment, set the arguments to the debugee (tshark) as required, you may need to point the debugger to the source file location, set breakpoints as required and you should be up and running.

answered 02 Dec '13, 02:48

grahamb's gravatar image

grahamb ♦
19.8k330206
accept rate: 22%