[asterisk-bugs] [Asterisk 0013300]: Asterisk crashes, leaving a voicemail message stored on pgsql DB via ODBC

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13300 
====================================================================== 
Reported By:                moliveras
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13300
Category:                   Applications/app_voicemail/ODBC
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     feedback
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 137188 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-08-13 12:32 CDT
Last Modified:              2008-08-15 09:00 CDT
====================================================================== 
Summary:                    Asterisk crashes, leaving a voicemail message stored
on pgsql DB via ODBC
Description: 
I compiled asterisk 2.4.21.1 for ODBC voicemail using a PGSQL DB. Every
time I left a voicemail message, asterisk would get a segmentation fault
and restart.  

I also tried this with the 1.4 branch and got the same result
(branch1.4-r137188).

The odd thing is that after compiling a NON OPTIMIZED build to get a
backtrace the crash no longer occurs.  I left over 150 messages with the
non optimized build and saw no problems.  Using the OPTIMIZED build crashes
asterisk ever time after the first voicemail message is left.  I will
attach the OPTIMIZED backtrace as that was all I could get.  Let me know
what additional data you would like to see and I will also attach it.

Best Regards,

Mike Oliveras


====================================================================== 

---------------------------------------------------------------------- 
 (0091443) Corydon76 (administrator) - 2008-08-15 09:00
 http://bugs.digium.com/view.php?id=13300#c91443 
---------------------------------------------------------------------- 
The results of this valgrind output suggests that there was no memory error
condition detected.  The key to this is noting that other than the dlopen
errors and the invalid fd errors, no other exceptional memory conditions
were detected.  The one I would have expected is an "invalid write". 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-08-15 09:00 Corydon76      Note Added: 0091443                          
======================================================================