Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
T
TLMSP curl
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
CYBER - Cyber Security
TS 103 523 MSP
TLMSP
TLMSP curl
Commits
a7349a48
Commit
a7349a48
authored
21 years ago
by
Daniel Stenberg
Browse files
Options
Downloads
Patches
Plain Diff
minor edits
parent
8042cd93
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/BUGS
+8
-9
8 additions, 9 deletions
docs/BUGS
with
8 additions
and
9 deletions
docs/BUGS
+
8
−
9
View file @
a7349a48
...
...
@@ -8,7 +8,7 @@ $Id$
BUGS
Curl and libcurl have grown substantially since the beginning. At the time
of writing (
end of March
2003), there are
35
000 lines of source code, and by
of writing (
August
2003), there are
about 40
000 lines of source code, and by
the time you read this it has probably grown even more.
Of course there are lots of bugs left. And lots of misfeatures.
...
...
@@ -32,7 +32,7 @@ WHERE 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
bad behavior. You therefore need to tell us:
...
...
@@ -48,16 +48,15 @@ WHAT TO REPORT
enable us to help you quicker and more accurately.
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
flag. Usually, you also get more info by using -i so that is likely to be
useful when reporting bugs as well.
debug dump with your bug report. The output you get by using the -v or
--trace options.
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
setup as you, we can't do much with it.
What we i
nstead ask
of
you
is
to get
a stack
trace and send that (much smaller) output to us instead!
setup as you, we can't do much with it.
I
nstead
we
ask you to get
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
s are
detailed in the
MANUAL file.
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
well, remove -O, -O2 etc from the compiler options.
Run the program until it
dumps
core.
Run the program until it core
s
.
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
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment