User Guide

Introduction

1. The version number of Wireshark and the dependent libraries linked with it, e.g. GTK+, etc. You can

obtain this from the about dialog box of Wireshark, or with the command wireshark -v.

2. Information about the platform you run Wireshark on.

3. A detailed description of your problem.

4. If you get an error/warning message, copy the text of that message (and also a few lines before and after

it, if there are some), so others may find the place where things go wrong. Please don't give something

like: "I get a warning while doing x" as this won't give a good idea where to look at.

Don't send large files!

Do not send large files (>100KB) to the mailing lists, just place a note that further data

is available on request. Large files will only annoy a lot of people on the list who are not

interested in your specific problem. If required, you will be asked for further data by the

persons who really can help you.

Don't send confidential information!

If you send captured data to the mailing lists, be sure they don't contain any sensitive or

confidential information like passwords or such.

1.6.7. Reporting Crashes on UNIX/Linux platforms

When reporting crashes with Wireshark, it is helpful if you supply the traceback information (besides the

information mentioned in "Reporting Problems").

You can obtain this traceback information with the following commands:

$ gdb `whereis wireshark | cut -f2 -d: | cut -d' ' -f2` core >& bt.txt

backtrace

Note

Type the characters in the first line verbatim! Those are back-tics there!

Note

backtrace is a gdb command. You should enter it verbatim after the first line shown above,

but it will not be echoed. The ^D (Control-D, that is, press the Control key and the D key

together) will cause gdb to exit. This will leave you with a file called bt.txt in the current

directory. Include the file with your bug report.

Note

If you do not have gdb available, you will have to check out your operating system's

debugger.

You should mail the traceback to the wireshark-dev[AT]wireshark.org mailing list.