Also available is proto_tree_add_debug_text(tree, format) which will display debug message right in the place. put ws_log statements in your code ( ws_debug, ws_info, ws_message, etc…, see wsutil/wslog.h) or g_print.$ tshark -log-level=noisy -log-domain=main,capture -log-file=/tmp/wsdebug -r some.pcap Level 'noisy' usually more useful if you know what you are looking for and can filter log output to a specific domain. The log levels available by increasing verbosity are 'critical', 'warning', 'message' (default), 'info', 'debug' and 'noisy'. The domain filter accepts a comma separated list of domains. You can filter the domain using -log-domains= or WIRESHARK_LOG_DOMAINS=.

You can filter the log level using the command-line option -log-level= or the environment variable WIRESHARK_LOG_LEVEL=. Wireshark logging broadly adopts the concept of domain and level from the GLib Messages and Logging API.Change Value to 'ALWAYS' and click the Ok button. In the Search: box enter 'console', then select gui.console_open in the search results. Start Wireshark and go to Edit->Preferences…->Advanced. Open up the console (needed for Windows only):

In these cases printf can be your best friend. Sometimes you just want to peek at some variables to see whats going on in your code, without the need for a heavy duty debugger session.

**Obsolete** Using the MSVC6 'source browser' capability.

Running dumpcap on Linux as unprivileged user.

Building without optimizations using autotools.

Building without optimizations using cmake.

Wireshark https logging