Wireshark - 0.99.7 Guide de l'utilisateur télécharger pdf (Page 26)

and after it, if there are some), so others may find the build step where things go wrong. Please

don't give something like: "I get a warning when compiling x" as this won't give any direction

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, or add it to your bug report, be sure it

doesn't contain any sensitive or confidential information, such as passwords.

1.7.8. 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 Section 1.7.7, “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, or append it to

your bug report.

1.7.9. 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 from Section 1.7.7, “Reporting Problems”.

Introduction

1 2 ... 21 22 23 24 25 26 27 28 29 30 31 ... 146 147

Pas de commentaire

Wireshark - 0.99.7 Guide de l'utilisateur Page 26