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

minor edits

Browse Source
This commit is contained in:
Daniel Stenberg 2003-08-18 15:24:46 +00:00
parent 8042cd93c3
commit a7349a48ff
1 changed files with 8 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
docs/BUGS
View File

@ -8,7 +8,7 @@ $Id$
BUGS BUGS
Curl and libcurl have grown substantially since the beginning. At the time Curl and libcurl have grown substantially since the beginning. At the time
of writing (end of March 2003), there are 35000 lines of source code, and by of writing (August 2003), there are about 40000 lines of source 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.
@ -32,7 +32,7 @@ WHERE TO REPORT
WHAT TO REPORT WHAT TO REPORT
When reporting a bug, you should include information that will help us When reporting a bug, you should include all information that will help us
understand what's wrong, what you expected to happen and how to repeat the understand what's wrong, what you expected to happen and how to repeat the
bad behavior. You therefore need to tell us: bad behavior. You therefore need to tell us:
@ -48,16 +48,15 @@ WHAT TO REPORT
enable us to help you quicker and more accurately. enable us to help you quicker and more accurately.
Since curl deals with networks, it often helps us if you include a protocol Since curl deals with networks, it often helps us if you include a protocol
debug dump with your bug report. The output you get by using the -v debug dump with your bug report. The output you get by using the -v or
flag. Usually, you also get more info by using -i so that is likely to be --trace options.
useful when reporting bugs as well.
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
setup as you, we can't do much with it. What we instead ask of you is to get setup as you, we can't do much with it. Instead we ask you to get a stack
a stack trace and send that (much smaller) output to us instead! 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 lists are detailed in the
MANUAL file. MANUAL file.
HOW TO GET A STACK TRACE HOW TO GET A STACK TRACE
@ -66,7 +65,7 @@ HOW TO GET A STACK TRACE
don't 'strip' the final executable. Try to avoid optimizing the code as don't 'strip' the final executable. Try to avoid optimizing the code as
well, remove -O, -O2 etc from the compiler options. well, remove -O, -O2 etc from the compiler options.
Run the program until it dumps core. Run the program until it cores.
Run your debugger on the core file, like '<debugger> curl core'. <debugger> 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 should be replaced with the name of your debugger, in most cases that will