Home | History | Annotate | Download | only in docs

Lines Matching full:your

35   have a go at a solution. You can optionally also post your bug/problem at
51 - your operating system's name and version number
62 and pieces in your report. You will benefit from this yourself, as it will
66 debug dump with your bug report. The output you get by using the -v or
81 When you've written your own application with libcurl to perform transfers,
84 Tell us the libcurl version and your operating system. Tell us the name and
86 you're using and what name resolving your libcurl uses. If you use SFTP or
89 Showing us a real source code example repeating your problem is the best way
91 your problem and to work on a fix (if we agree it truly is a problem).
94 of the libcurl API or other malfunctions in your applications. It is advised
95 that you run your problematic program using a memory debug tool like
126 Run your debugger on the core file, like '<debugger> curl core'. <debugger>
127 should be replaced with the name of your debugger, in most cases that will
135 crashed. Include the stack trace with your detailed bug report. It'll help a
145 please convert your program over to plain C and follow the steps outlined