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

I want to debug my plugin but couldn't find debug console option in EDIT|Preference

asked 06 Nov '12, 22:28

Akhil's gravatar image

Akhil
53272831
accept rate: 0%

edited 07 Nov '12, 00:30

grahamb's gravatar image

grahamb ♦
19.8k330206


I have said the same in the other question of yours. Go to "Edit->Preference". In the option "Open a console window", change it from "Never" to "Always(debugging)" and click "Apply"

permanent link

answered 07 Nov '12, 02:56

SidR's gravatar image

SidR
245121722
accept rate: 30%

In ubuntu option "Open a console window" is not present

(07 Nov '12, 22:51) Akhil

Linux doesn't need this option, just launch Wireshark from a terminal window.

permanent link

answered 07 Nov '12, 03:50

Jaap's gravatar image

Jaap ♦
11.7k16101
accept rate: 14%

I am launching wireshark from terminal. what should i do after that to start debugging??????

(08 Nov '12, 00:51) Akhil

As already answered in the following question:

http://ask.wireshark.org/questions/15602/how-to-debug-my-plugin

You need to add debug statements to your code to see some output in the debug console.

http://wiki.wireshark.org/Development/Tips

Please read the Developer Guide thoroughly.

BTW: Is it really necessary to add 5-6 question marks (?????) to your questions? One should be sufficient to properly flag your sentence as a question ;-)

(08 Nov '12, 01:15) Kurt Knochner ♦

I have added the "g_print " statemnet in my code. But the debug console is not opened.

(08 Nov '12, 03:00) Akhil

Did you start Wireshark from a console window? Are you sure the g_print statement is executed?

(08 Nov '12, 04:10) Kurt Knochner ♦

Yes i started Wireshark from a console window. and the g_print statement is executed

(08 Nov '12, 04:34) Akhil

well, I don't know what's wrong with your code or system, but if I add the following statement to the TCP dissector, I get a message on the console every time the dissector gets executed.

g_print("[INFO] Entering TCP dissector\n");

Maybe you try it with a standard dissector first, to see if there is a general problem with your code and/or system. If that works, it should work within your dissector as well. If it does not work, your g_print code is not executed.

Regards
Kurt

(08 Nov '12, 05:32) Kurt Knochner ♦
showing 5 of 6 show 1 more comments
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×4

question asked: 06 Nov '12, 22:28

question was seen: 3,448 times

last updated: 08 Nov '12, 05:55

p​o​w​e​r​e​d by O​S​Q​A