Lines Matching full:that
35 means that bugs will sneak in, no matter how hard we try not to.
51 Please read the rest of this document below first before doing that!
58 If you find a bug or problem in curl or libcurl that you think has a
59 security impact, for example a bug that can put users in danger or make them
60 vulnerable if the bug becomes public knowledge, then please report that bug
63 Security related bugs or bugs that are suspected to have a security impact,
64 should be reported by email to curl-security@haxx.se so that they first can
75 When reporting a bug, you should include all information that will help us
83 - versions of the used libraries that libcurl is built to use
98 send that huge file to anyone of us. Unless we have an exact same system
100 trace and send that (much smaller) output to us instead!
119 Lots of problems that appear to be libcurl problems are actually just abuses
121 that you run your problematic program using a memory debug tool like
130 There are no developers in the curl project that are paid to work on bugs.
131 All developers that take on reported bugs do this on a voluntary basis. We
135 But please do not assume that you can just lump over something to us and it
146 First, you must make sure that you compile all sources with -g and that you
153 should be replaced with the name of your debugger, in most cases that will
159 The list that is presented is the stack trace. If everything worked, it is
160 supposed to contain the chain of functions that were called when curl
167 primarily approach the team that works on that particular binding and see
170 If you suspect that the problem exists in the underlying libcurl, then
182 old versions when chances are we already fixed them or at least that they've
187 issue. If that version number shows us that you're using an out-of-date
195 At times people insist that they cannot upgrade to a modern curl version,
196 but instead they "just want the bug fixed". That's fine, just don't count on
197 us spending many cycles on trying to identify which single commit, if that's
198 even possible, that at some point in the past fixed the problem you're now
215 In the issue tracker you can expect that some labels will be set on the
221 that someone will ask follow-up questions. Which version did you use? Which
227 about the problem, so that we can help you figure it out. Or maybe you can
233 For problems that we can't reproduce and can't understand even after having
242 for discussing possible ways to move forward with the task, we take that as
243 a strong suggestion that the bug is not important.
251 Bugs that are filed and are understood can unfortunately end up in the
253 perfectly valid problems that *should* get fixed but apparently aren't. We
260 This is a list of known bugs. Bugs we know exist and that have been pointed
261 out but that haven't yet been fixed. The reasons for why they haven't been
262 fixed can involve anything really, but the primary reason is that nobody has
273 Issues that are filed or reported that aren't really bugs but more missing
281 take up a discussion with the curl development team on how that could be
282 implemented or provided in the project so that you can work on ticking it
283 odd that document.
292 actually is, but they're at least not completely dead). Those that are
