[asterisk-bugs] [Asterisk 0017387]: crash today using curl

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17387 
====================================================================== 
Reported By:                jmls
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17387
Category:                   Functions/func_curl
Reproducibility:            random
Severity:                   crash
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 259858 
Request Review:              
====================================================================== 
Date Submitted:             2010-05-24 13:04 CDT
Last Modified:              2010-05-25 06:13 CDT
====================================================================== 
Summary:                    crash today using curl
Description: 
asterisk segfaulted. from the backtrace looks like curl was involved.
Please see attached back trace
====================================================================== 

---------------------------------------------------------------------- 
 (0122359) davidw (reporter) - 2010-05-25 06:13
 https://issues.asterisk.org/view.php?id=17387#c122359 
---------------------------------------------------------------------- 
I suspect it will help if you print the values of the parameters to
curl_easy_perform, from frame 8, including the result of at least a single
indirection on any pointers.

Could you also confirm that this is a seg-fault, rather than, say an
abort.  free() normally fails by issuing abort(), then again, you normally
see the abort() call on the stack.  (A lot of people call all core dumps
seg-faults!)

Also have a look at doc/valgrind.txt.  As this is memory management
related, you may be asked to follow that procedure. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-05-25 06:13 davidw         Note Added: 0122359                          
======================================================================