Go to the first, previous, next, last section, table of contents.
You are welcome to send bug reports about GNU Wget to
bug-wget@gnu.org.
Before actually submitting a bug report, please try to follow a few
simple guidelines.
-
Please try to ascertain that the behaviour you see really is a bug. If
Wget crashes, it's a bug. If Wget does not behave as documented,
it's a bug. If things work strange, but you are not sure about the way
they are supposed to work, it might well be a bug.
-
Try to repeat the bug in as simple circumstances as possible. E.g. if
Wget crashes while downloading `wget -rl0 -kKE -t5 -Y0
http://yoyodyne.com -o /tmp/log', you should try to see if the crash is
repeatable, and if will occur with a simpler set of options. You might
even try to start the download at the page where the crash occurred to
see if that page somehow triggered the crash.
Also, while I will probably be interested to know the contents of your
`.wgetrc' file, just dumping it into the debug message is probably
a bad idea. Instead, you should first try to see if the bug repeats
with `.wgetrc' moved out of the way. Only if it turns out that
`.wgetrc' settings affect the bug, mail me the relevant parts of
the file.
-
Please start Wget with `-d' option and send the log (or the
relevant parts of it). If Wget was compiled without debug support,
recompile it. It is much easier to trace bugs with debug support
on.
-
If Wget has crashed, try to run it in a debugger, e.g.
gdb `which
wget` core and type where to get the backtrace.
Go to the first, previous, next, last section, table of contents.