User Guide

Introduction

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.

1.6.8. Reporting Crashes on Windows platforms

The Windows distributions don't contain the symbol files (.pdb), because they are very large. For this

reason it's not possible to create a meaningful backtrace file from it. You should report your crash just like

other problems, using the mechanism described above.