moparisthebest/curl
1
0
Fork 0
mirror of https://github.com/moparisthebest/curl synced 2024-12-21 23:58:49 -05:00
Code Issues Releases Wiki Activity

updated

Browse Source
This commit is contained in:
Daniel Stenberg 2001-03-12 09:42:22 +00:00
parent e9b763ff05
commit b5ba011110
1 changed files with 9 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
docs/BUGS
View File

@ -6,9 +6,9 @@
BUGS BUGS
Curl has grown substantially from that day, several years ago, when I Curl and libcurl have grown substantially since the beginning. At the time
started fiddling with it. When I write this, there are 16500 lines of source of writing (mid March 2001), there are 23000 lines of source code, and by
code, and by the time you read this it has probably grown even more. the time you read this it has probably grown even more.
Of course there are lots of bugs left. And lots of misfeatures. Of course there are lots of bugs left. And lots of misfeatures.
@ -21,10 +21,11 @@ BUGS
http://sourceforge.net/bugs/?group_id=976 http://sourceforge.net/bugs/?group_id=976
When reporting a bug, you should include information that will help us When reporting a bug, you should include information that will help us
understand what's wrong, what's expected and how to repeat it. You therefore understand what's wrong, what you expected to happen and how to repeat the
need to supply your operating system's name and version number (uname -a bad behaviour. You therefore need to supply your operating system's name and
under a unix is fine), what version of curl you're using (curl -v is fine), version number (uname -a under a unix is fine), what version of curl you're
what URL you were working with and anything else you think matters. using (curl -V is fine), what URL you were working with and anything else
you think matters.
If curl crashed, causing a core dump (in unix), there is hardly any use to 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 send that huge file to anyone of us. Unless we have an exact same system
@ -32,7 +33,7 @@ BUGS
a stack trace and send that (much smaller) output to us instead! a stack trace and send that (much smaller) output to us instead!
The address and how to subscribe to the mailing list is detailed in the The address and how to subscribe to the mailing list is detailed in the
README.curl file. MANUAL file.
HOW TO GET A STACK TRACE with a common unix debugger HOW TO GET A STACK TRACE with a common unix debugger
==================================================== ====================================================