2010-02-14 22:40:18 +03:00
|
|
|
_ _ ____ _
|
|
|
|
___| | | | _ \| |
|
|
|
|
/ __| | | | |_) | |
|
|
|
|
| (__| |_| | _ <| |___
|
2000-05-22 21:35:35 +04:00
|
|
|
\___|\___/|_| \_\_____|
|
|
|
|
|
|
|
|
BUGS
|
|
|
|
|
2011-09-13 01:02:41 +04:00
|
|
|
1. Bugs
|
|
|
|
1.1 There are still bugs
|
|
|
|
1.2 Where to report
|
|
|
|
1.3 What to report
|
|
|
|
1.4 libcurl problems
|
|
|
|
1.5 Who will fix the problems
|
|
|
|
1.6 How to get a stack trace
|
|
|
|
1.7 Bugs in libcurl bindings
|
2011-09-13 00:55:40 +04:00
|
|
|
|
|
|
|
==============================================================================
|
|
|
|
|
2011-09-13 01:02:41 +04:00
|
|
|
1.1 There are still bugs
|
2011-09-13 00:55:40 +04:00
|
|
|
|
2001-03-12 12:42:22 +03:00
|
|
|
Curl and libcurl have grown substantially since the beginning. At the time
|
2013-01-14 02:16:11 +04:00
|
|
|
of writing (January 2013), there are about 83,000 lines of source code, and
|
2011-09-13 00:55:40 +04:00
|
|
|
by the time you read this it has probably grown even more.
|
2000-05-22 21:35:35 +04:00
|
|
|
|
|
|
|
Of course there are lots of bugs left. And lots of misfeatures.
|
|
|
|
|
|
|
|
To help us make curl the stable and solid product we want it to be, we need
|
2002-04-27 22:31:49 +04:00
|
|
|
bug reports and bug fixes.
|
|
|
|
|
2011-09-13 01:02:41 +04:00
|
|
|
1.2 Where to report
|
2002-04-27 22:31:49 +04:00
|
|
|
|
|
|
|
If you can't fix a bug yourself and submit a fix for it, try to report an as
|
2003-03-26 14:44:04 +03:00
|
|
|
detailed report as possible to a curl mailing list to allow one of us to
|
2011-09-13 00:55:40 +04:00
|
|
|
have a go at a solution. You can optionally also post your bug/problem at
|
|
|
|
curl's bug tracking system over at
|
2000-05-22 21:35:35 +04:00
|
|
|
|
2013-01-14 02:16:11 +04:00
|
|
|
https://sourceforge.net/p/curl/bugs/
|
2000-05-22 21:35:35 +04:00
|
|
|
|
2012-11-02 00:33:37 +04:00
|
|
|
Please read the rest of this document below first before doing that! Also,
|
|
|
|
you need to login to your sourceforge account before being able to submit a
|
|
|
|
bug report (necessary evil done to avoid spam).
|
2003-03-26 14:44:04 +03:00
|
|
|
|
|
|
|
If you feel you need to ask around first, find a suitable mailing list and
|
|
|
|
post there. The lists are available on http://curl.haxx.se/mail/
|
2002-04-27 22:31:49 +04:00
|
|
|
|
2011-09-13 01:02:41 +04:00
|
|
|
1.3 What to report
|
2002-04-27 22:31:49 +04:00
|
|
|
|
2003-08-18 19:24:46 +04:00
|
|
|
When reporting a bug, you should include all information that will help us
|
2003-03-26 14:44:04 +03:00
|
|
|
understand what's wrong, what you expected to happen and how to repeat the
|
2002-04-27 22:31:49 +04:00
|
|
|
bad behavior. You therefore need to tell us:
|
|
|
|
|
2011-09-13 15:05:31 +04:00
|
|
|
- your operating system's name and version number
|
|
|
|
|
2002-04-27 22:31:49 +04:00
|
|
|
- what version of curl you're using (curl -V is fine)
|
2011-09-13 15:05:31 +04:00
|
|
|
|
2007-07-20 01:35:36 +04:00
|
|
|
- versions of the used libraries that libcurl is built to use
|
2011-09-13 15:05:31 +04:00
|
|
|
|
2002-04-27 22:31:49 +04:00
|
|
|
- what URL you were working with (if possible), at least which protocol
|
|
|
|
|
|
|
|
and anything and everything else you think matters. Tell us what you
|
|
|
|
expected to happen, tell use what did happen, tell us how you could make it
|
|
|
|
work another way. Dig around, try out, test. Then include all the tiny bits
|
|
|
|
and pieces in your report. You will benefit from this yourself, as it will
|
|
|
|
enable us to help you quicker and more accurately.
|
|
|
|
|
|
|
|
Since curl deals with networks, it often helps us if you include a protocol
|
2003-08-18 19:24:46 +04:00
|
|
|
debug dump with your bug report. The output you get by using the -v or
|
|
|
|
--trace options.
|
2002-01-10 10:38:53 +03:00
|
|
|
|
2000-05-22 21:35:35 +04:00
|
|
|
If curl crashed, causing a core dump (in unix), there is hardly any use to
|
|
|
|
send that huge file to anyone of us. Unless we have an exact same system
|
2003-08-18 19:24:46 +04:00
|
|
|
setup as you, we can't do much with it. Instead we ask you to get a stack
|
|
|
|
trace and send that (much smaller) output to us instead!
|
2000-05-22 21:35:35 +04:00
|
|
|
|
2003-08-18 19:24:46 +04:00
|
|
|
The address and how to subscribe to the mailing lists are detailed in the
|
2001-03-12 12:42:22 +03:00
|
|
|
MANUAL file.
|
2000-05-22 21:35:35 +04:00
|
|
|
|
2011-09-13 01:02:41 +04:00
|
|
|
1.4 libcurl problems
|
2011-09-13 00:55:40 +04:00
|
|
|
|
|
|
|
First, post all libcurl problems on the curl-library mailing list.
|
|
|
|
|
|
|
|
When you've written your own application with libcurl to perform transfers,
|
|
|
|
it is even more important to be specific and detailed when reporting bugs.
|
|
|
|
|
|
|
|
Tell us the libcurl version and your operating system. Tell us the name and
|
|
|
|
version of all relevant sub-components like for example the SSL library
|
|
|
|
you're using and what name resolving your libcurl uses. If you use SFTP or
|
|
|
|
SCP, the libssh2 version is relevant etc.
|
|
|
|
|
|
|
|
Showing us a real source code example repeating your problem is the best way
|
|
|
|
to get our attention and it will greatly increase our chances to understand
|
|
|
|
your problem and to work on a fix (if we agree it truly is a problem).
|
|
|
|
|
|
|
|
Lots of problems that appear to be libcurl problems are actually just abuses
|
2012-07-20 23:02:58 +04:00
|
|
|
of the libcurl API or other malfunctions in your applications. It is advised
|
2011-09-13 00:55:40 +04:00
|
|
|
that you run your problematic program using a memory debug tool like
|
|
|
|
valgrind or similar before you post memory-related or "crashing" problems to
|
|
|
|
us.
|
|
|
|
|
2011-09-13 01:02:41 +04:00
|
|
|
1.5 Who will fix the problems
|
2011-09-13 00:55:40 +04:00
|
|
|
|
|
|
|
If the problems or bugs you describe are considered to be bugs, we want to
|
|
|
|
have the problems fixed.
|
|
|
|
|
|
|
|
There are no developers in the curl project that are paid to work on bugs.
|
2011-09-13 15:05:31 +04:00
|
|
|
All developers that take on reported bugs do this on a voluntary basis. We
|
2011-09-13 00:55:40 +04:00
|
|
|
do it out of an ambition to keep curl and libcurl excellent products and out
|
|
|
|
of pride.
|
|
|
|
|
|
|
|
But please do not assume that you can just lump over something to us and it
|
|
|
|
will then magically be fixed after some given time. Most often we need
|
|
|
|
feedback and help to understand what you've experienced and how to repeat a
|
|
|
|
problem. Then we may only be able to assist YOU to debug the problem and to
|
|
|
|
track down the proper fix.
|
|
|
|
|
|
|
|
We get reports from many people every month and each report can take a
|
|
|
|
considerable amount of time to really go to the bottom with.
|
|
|
|
|
2011-09-13 01:02:41 +04:00
|
|
|
1.6 How to get a stack trace
|
2000-05-22 21:35:35 +04:00
|
|
|
|
|
|
|
First, you must make sure that you compile all sources with -g and that you
|
2001-12-03 12:44:11 +03:00
|
|
|
don't 'strip' the final executable. Try to avoid optimizing the code as
|
|
|
|
well, remove -O, -O2 etc from the compiler options.
|
2000-05-22 21:35:35 +04:00
|
|
|
|
2003-08-18 19:24:46 +04:00
|
|
|
Run the program until it cores.
|
2000-05-22 21:35:35 +04:00
|
|
|
|
|
|
|
Run your debugger on the core file, like '<debugger> curl core'. <debugger>
|
|
|
|
should be replaced with the name of your debugger, in most cases that will
|
|
|
|
be 'gdb', but 'dbx' and others also occur.
|
|
|
|
|
|
|
|
When the debugger has finished loading the core file and presents you a
|
2001-12-03 12:44:11 +03:00
|
|
|
prompt, enter 'where' (without the quotes) and press return.
|
2000-05-22 21:35:35 +04:00
|
|
|
|
|
|
|
The list that is presented is the stack trace. If everything worked, it is
|
|
|
|
supposed to contain the chain of functions that were called when curl
|
2001-12-03 12:44:11 +03:00
|
|
|
crashed. Include the stack trace with your detailed bug report. It'll help a
|
|
|
|
lot.
|
2000-05-22 21:35:35 +04:00
|
|
|
|
2011-09-13 01:02:41 +04:00
|
|
|
1.7 Bugs in libcurl bindings
|
2011-09-13 00:55:40 +04:00
|
|
|
|
|
|
|
There will of course pop up bugs in libcurl bindings. You should then
|
|
|
|
primarily approach the team that works on that particular binding and see
|
|
|
|
what you can do to help them fix the problem.
|
|
|
|
|
|
|
|
If you suspect that the problem exists in the underlying libcurl, then
|
|
|
|
please convert your program over to plain C and follow the steps outlined
|
|
|
|
above.
|