wget: Reporting Bugs

1 
1 8.6 Reporting Bugs
1 ==================
1 
1 You are welcome to submit bug reports via the GNU Wget bug tracker (see
1 <https://savannah.gnu.org/bugs/?func=additem&group=wget>) or to our
1 mailing list <bug-wget@gnu.org>.
1 
1    Visit <https://lists.gnu.org/mailman/listinfo/bug-wget> to get more
1 info (how to subscribe, list archives, ...).
1 
1    Before actually submitting a bug report, please try to follow a few
1 simple guidelines.
1 
1   1. Please try to ascertain that the behavior you see really is a bug.
1      If Wget crashes, it’s a bug.  If Wget does not behave as
1      documented, it’s a bug.  If things work strange, but you are not
1      sure about the way they are supposed to work, it might well be a
1      bug, but you might want to double-check the documentation and the
1      mailing lists (⇒Mailing Lists).
1 
1   2. Try to repeat the bug in as simple circumstances as possible.  E.g.
1      if Wget crashes while downloading ‘wget -rl0 -kKE -t5 --no-proxy
1      http://example.com -o /tmp/log’, you should try to see if the crash
1      is repeatable, and if will occur with a simpler set of options.
1      You might even try to start the download at the page where the
1      crash occurred to see if that page somehow triggered the crash.
1 
1      Also, while I will probably be interested to know the contents of
1      your ‘.wgetrc’ file, just dumping it into the debug message is
1      probably a bad idea.  Instead, you should first try to see if the
1      bug repeats with ‘.wgetrc’ moved out of the way.  Only if it turns
1      out that ‘.wgetrc’ settings affect the bug, mail me the relevant
1      parts of the file.
1 
1   3. Please start Wget with ‘-d’ option and send us the resulting output
1      (or relevant parts thereof).  If Wget was compiled without debug
1      support, recompile it—it is _much_ easier to trace bugs with debug
1      support on.
1 
1      Note: please make sure to remove any potentially sensitive
1      information from the debug log before sending it to the bug
1      address.  The ‘-d’ won’t go out of its way to collect sensitive
1      information, but the log _will_ contain a fairly complete
1      transcript of Wget’s communication with the server, which may
1      include passwords and pieces of downloaded data.  Since the bug
1      address is publically archived, you may assume that all bug reports
1      are visible to the public.
1 
1   4. If Wget has crashed, try to run it in a debugger, e.g.  ‘gdb `which
1      wget` core’ and type ‘where’ to get the backtrace.  This may not
1      work if the system administrator has disabled core files, but it is
1      safe to try.
1