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

wireshark-announce This mailing list will inform you about new program releases, which

usually appear about every 4-8 weeks.

wireshark-users This list is for users of Wireshark. People post questions about build-

ing and using Wireshark, others (hopefully) provide answers.

wireshark-dev This list is for Wireshark developers. People post questions about the

development of Wireshark, others (hopefully) provide answers. If you

want to start developing a protocol dissector, join this list.

wireshark-bugs This list is for Wireshark developers. Everytime a change to the bug

database occurs, a mail to this mailing list is generated. If you want to

be notified about all the changes to the bug database, join this list. De-

tails about the bug database can be found in Section 1.7.6, “Bug data-

base (Bugzilla)”.

wireshark-commits This list is for Wireshark developers. Everytime a change to the SVN

repository is checked in, a mail to this mailing list is generated. If you

want to be notified about all the changes to the SVN repository, join

this list. Details about the SVN repository can be found in Section 3.2,

“The Wireshark Subversion repository”.

You can subscribe to each of these lists from the Wireshark web site: http://www.wireshark.org.

Simply select the mailing lists link on the left hand side of the site. The lists are archived at the

Wireshark web site as well.

Tip!

You can search in the list archives to see if someone previously asked the same ques-

tion and maybe already got an answer. That way you don't have to wait until someone

answers your question.

1.7.6. Bug database (Bugzilla)

The Wireshark community collects bug reports in a Bugzilla database at http://bugs.wireshark.org.

This database is filled with manually filed bug reports, usually after some discussion on wireshark-

dev, and bug reports from the QA build tools.

1.7.7. Reporting Problems

Note!

Before reporting any problems, please make sure you have installed the latest version

of Wireshark.

If you report problems, provide as much information as possible. In general, just think about what

you would need to find that problem, if someone else sends you such a problem report. Also keep in

mind that people compile/run Wireshark on a lot of different platforms.

When reporting problems with Wireshark, it is helpful if you supply the following information:

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

You can obtain this 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

Introduction

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

Pas de commentaire

Wireshark - 0.99.7 Guide de l'utilisateur Page 25