/usr/share/doc/wireshark-doc/wsdg_html_chunked/ChIntroHelp.html is in wireshark-doc 1.10.6-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 | <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>1.7. Reporting problems and getting help</title><link rel="stylesheet" type="text/css" href="ws.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><link rel="home" href="index.html" title="Wireshark Developer's Guide"><link rel="up" href="ChapterIntroduction.html" title="Chapter 1. Introduction"><link rel="prev" href="ChIntroAutomated.html" title="1.6. Automated Builds (Buildbot)"><link rel="next" href="ChapterSetup.html" title="Chapter 2. Quick Setup"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">1.7. Reporting problems and getting help</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ChIntroAutomated.html">Prev</a> </td><th width="60%" align="center">Chapter 1. Introduction</th><td width="20%" align="right"> <a accesskey="n" href="ChapterSetup.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="ChIntroHelp"></a>1.7. Reporting problems and getting help</h2></div></div></div><p>
If you have problems, or need help with Wireshark, there are several
places that may be of interest to you (well, beside this guide of
course).
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="ChIntroHomepage"></a>1.7.1. Website</h3></div></div></div><p>
You will find lot's of useful information on the Wireshark homepage at
<a class="ulink" href="http://www.wireshark.org" target="_top">http://www.wireshark.org</a>.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="ChIntroWiki"></a>1.7.2. Wiki</h3></div></div></div><p>
The Wireshark Wiki at <a class="ulink" href="http://wiki.wireshark.org" target="_top">http://wiki.wireshark.org</a> provides a wide range
of information related to Wireshark and packet capturing in general.
You will find a lot of information not part of this developer's guide. For
example, there is an explanation how to capture on a switched network,
an ongoing effort to build a protocol reference and a lot more.
</p><p>
And best of all, if you would like to contribute your knowledge on a
specific topic (maybe a network protocol you know well), you can edit the
wiki pages by simply using your webbrowser.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="ChIntroFAQ"></a>1.7.3. FAQ</h3></div></div></div><p>
The "Frequently Asked Questions" will list often asked questions and
the corresponding answers.
</p><p>
Before sending any mail to the mailing lists below, be sure to read the
FAQ, as it will often answer the question(s) you might have. This will save
yourself and others a lot of time (keep in mind that a lot of people are
subscribed to the mailing lists).
</p><p>
You will find the FAQ inside Wireshark by clicking the menu item
Help/Contents and selecting the FAQ page in the upcoming dialog.
</p><p>
An online version is available at the Wireshark website:
<a class="ulink" href="http://www.wireshark.org/faq.html" target="_top">http://www.wireshark.org/faq.html</a>. You might
prefer this online version, as it's typically more up to date and the HTML
format is easier to use.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="ChIntroOtherSources"></a>1.7.4. Other sources</h3></div></div></div><p>
If you don't find the information you need inside this book, there are
various other sources of information:
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
the file <code class="filename">doc/README.developer</code> and
all the other README.xxx files in the source code - these are various
documentation files on different topics
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note: Read the README!"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="wsdg_graphics/note.png"></td><th align="left">Read the README!</th></tr><tr><td align="left" valign="top"><p>
The README.developer is packed full with all kinds of details relevant
to the developer of Wireshark source code. It advices you around common
pitfalls, shows you basic layout of dissector code, shows details of the
API's available to the dissector developer, etc.
</p></td></tr></table></div></li><li class="listitem"><p>
the Wireshark source code
</p></li><li class="listitem"><p>
tool documentation of the various tools used
(e.g. manpages of sed, gcc, ...)
</p></li><li class="listitem"><p>
the different mailing lists: see <a class="xref" href="ChIntroHelp.html#ChIntroMailingLists" title="1.7.5. Mailing Lists">Section 1.7.5, “Mailing Lists”</a>
</p></li><li class="listitem"><p>
...
</p></li></ul></div><p>
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="ChIntroMailingLists"></a>1.7.5. Mailing Lists</h3></div></div></div><p>
There are several mailing lists available on specific Wireshark topics:
</p><div class="variablelist"><dl class="variablelist"><dt><span class="term"><span class="command"><strong>wireshark-announce</strong></span></span></dt><dd><p>
This mailing list will inform you about new program
releases, which usually appear about every 4-8 weeks.
</p></dd><dt><span class="term"><span class="command"><strong>wireshark-users</strong></span></span></dt><dd><p>
This list is for users of Wireshark. People post
questions about building and using Wireshark, others (hopefully)
provide answers.
</p></dd><dt><span class="term"><span class="command"><strong>wireshark-dev</strong></span></span></dt><dd><p>
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.
</p></dd><dt><span class="term"><span class="command"><strong>wireshark-bugs</strong></span></span></dt><dd><p>
This list is for Wireshark developers. Every time 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. Details about the bug database can be
found in <a class="xref" href="ChIntroHelp.html#ChIntroBugDatabase" title="1.7.6. Bug database (Bugzilla)">Section 1.7.6, “Bug database (Bugzilla)”</a>.
</p></dd><dt><span class="term"><span class="command"><strong>wireshark-commits</strong></span></span></dt><dd><p>
This list is for Wireshark developers. Every time 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 <a class="xref" href="ChSrcSVNServer.html" title="3.2. The Wireshark Subversion repository">Section 3.2, “The Wireshark Subversion repository”</a>.
</p></dd></dl></div><p>
You can subscribe to each of these lists from the Wireshark web site:
<a class="ulink" href="http://www.wireshark.org" target="_top">http://www.wireshark.org</a>. Simply
select the <span class="command"><strong>mailing lists</strong></span> link on the left hand
side of the site. The lists are archived at the Wireshark web site
as well.
</p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Tip: Tip!"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Tip]" src="wsdg_graphics/tip.png"></td><th align="left">Tip!</th></tr><tr><td align="left" valign="top"><p>
You can search in the list archives to see if someone previously asked the same
question and maybe already got an answer. That way you
don't have to wait until someone answers your question.
</p></td></tr></table></div><p>
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="ChIntroBugDatabase"></a>1.7.6. Bug database (Bugzilla)</h3></div></div></div><p>
The Wireshark community collects bug reports in a Bugzilla database at
<a class="ulink" href="https://bugs.wireshark.org" target="_top">https://bugs.wireshark.org</a>.
This database is filled with manually filed bug reports, usually after some
discussion on wireshark-dev, and automatic bug reports from the buildbot tools.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="ChIntroReportProblems"></a>1.7.7. Reporting Problems</h3></div></div></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note: Note!"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="wsdg_graphics/note.png"></td><th align="left">Note!</th></tr><tr><td align="left" valign="top"><p>
Before reporting any problems, please make sure you have installed the
latest version of Wireshark. Reports on older maintainance releases are
usually met with an upgrade request.
</p></td></tr></table></div><p>
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.
</p><p>
When reporting problems with Wireshark, it is helpful if you supply the
following information:
</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>
The version number of Wireshark and the dependent libraries linked with
it, e.g. GTK+, etc. You can obtain this with the command
<span class="command"><strong>wireshark -v</strong></span>.
</p></li><li class="listitem"><p>
Information about the platform you run Wireshark on.
</p></li><li class="listitem"><p>
A detailed description of your problem.
</p></li><li class="listitem"><p>
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 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.
</p></li></ol></div><p>
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note: Don't send large files!"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="wsdg_graphics/note.png"></td><th align="left">Don't send large files!</th></tr><tr><td align="left" valign="top"><p>
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.
</p></td></tr></table></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note: Don't send confidential information!"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="wsdg_graphics/note.png"></td><th align="left">Don't send confidential information!</th></tr><tr><td align="left" valign="top"><p>
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. Visibility of such files can be limited to certain
groups in the Bugzilla database though.
</p></td></tr></table></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp21475892"></a>1.7.8. Reporting Crashes on UNIX/Linux platforms</h3></div></div></div><p>
When reporting crashes with Wireshark, it is helpful if you supply the
traceback information (besides the information mentioned in
<a class="xref" href="ChIntroHelp.html#ChIntroReportProblems" title="1.7.7. Reporting Problems">Section 1.7.7, “Reporting Problems”</a>).
</p><p>
You can obtain this traceback information with the following commands:
</p><pre class="programlisting">
$ gdb `whereis wireshark | cut -f2 -d: | cut -d' ' -f2` core >& bt.txt
backtrace
^D
$
</pre><p>
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="wsdg_graphics/note.png"></td><th align="left">Note</th></tr><tr><td align="left" valign="top"><p>
Type the characters in the first line verbatim! Those are
back-tics there!
</p></td></tr></table></div><p>
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="wsdg_graphics/note.png"></td><th align="left">Note</th></tr><tr><td align="left" valign="top"><p>
backtrace is a <span class="command"><strong>gdb</strong></span> 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 <span class="command"><strong>gdb</strong></span> to exit. This will
leave you with a file called
<code class="filename">bt.txt</code> in the current directory.
Include the file with your bug report.
</p></td></tr></table></div><p>
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="wsdg_graphics/note.png"></td><th align="left">Note</th></tr><tr><td align="left" valign="top"><p>
If you do not have <span class="command"><strong>gdb</strong></span> available, you
will have to check out your operating system's debugger.
</p></td></tr></table></div><p>
</p><p>
You should mail the traceback to the
<a class="ulink" href="mailto:wireshark-dev%5BAT%5Dwireshark.org" target="_top">wireshark-dev[AT]wireshark.org</a>
mailing list, or attach it to your bug report.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp21480772"></a>1.7.9. Reporting Crashes on Windows platforms</h3></div></div></div><p>
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
<a class="xref" href="ChIntroHelp.html#ChIntroReportProblems" title="1.7.7. Reporting Problems">Section 1.7.7, “Reporting Problems”</a>.
</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ChIntroAutomated.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ChapterIntroduction.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ChapterSetup.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">1.6. Automated Builds (Buildbot) </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 2. Quick Setup</td></tr></table></div></body></html>
|