[asterisk-bugs] [Asterisk 0016995]: [patch] Crash in app_voicemail.c in function retrieve_file (Read out in small chunks)

Asterisk Bug Tracker noreply at bugs.digium.com
Thu Jan 6 05:38:18 UTC 2011


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16995 
====================================================================== 
Reported By:                vrban
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16995
Category:                   Applications/app_voicemail/ODBC
Reproducibility:            random
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.4.29.1 
JIRA:                       SWP-2855 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-03-09 03:08 CST
Last Modified:              2011-01-05 23:38 CST
====================================================================== 
Summary:                    [patch] Crash in app_voicemail.c in function
retrieve_file  (Read out in small chunks)
Description: 
Every few days, one of my asterisk 1.4.29 crash with this error. See
bt_full.txt
Asterisk was compiled with DONT_OPTIMIZE, so all needed information should
be visible.
====================================================================== 

---------------------------------------------------------------------- 
 (0130241) tilghman (manager) - 2011-01-05 23:38
 https://issues.asterisk.org/view.php?id=16995#c130241 
---------------------------------------------------------------------- 
vrban: p_crasher2 still does not correctly simulate parallel queries.  A
condition broadcast may allow all the threads to start at the broadcast
time at the earliest, but as I stated before, if the entire set of commands
can occur in a single context switch, then it is still only serializing the
queries.  You need to ensure that each step is completed in tandem (and at
various offsets) using condition variables before you have a valid test of
multiple queries existing in various states in parallel.

pabelanger: the issue is still in triage state, as a cause has not been
determined. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-01-05 23:38 tilghman       Note Added: 0130241                          
======================================================================




More information about the asterisk-bugs mailing list