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

modified the stack trace section slightly

Browse Source
This commit is contained in:
Daniel Stenberg 2001-12-03 09:44:11 +00:00
parent 61e6554b7f
commit 4ec0401529
1 changed files with 9 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
docs/BUGS
View File

@ -1,3 +1,4 @@
$Id$
_ _ ____ _
___| | | | _ \| |
/ __| | | | |_) | |
@ -35,23 +36,24 @@ BUGS
The address and how to subscribe to the mailing list is detailed in the
MANUAL file.
HOW TO GET A STACK TRACE with a common unix debugger
====================================================
How To Get A Stack Trace
========================
First, you must make sure that you compile all sources with -g and that you
don't 'strip' the final executable.
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 bangs.
Run the program until it dumps core.
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
prompt, you can give the compiler instructions. Enter 'where' (without the
quotes) and press return.
prompt, enter 'where' (without the quotes) and press return.
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
crashed.
crashed. Include the stack trace with your detailed bug report. It'll help a
lot.