[asterisk-bugs] [Asterisk 0018240]: VoicemailMain Exits Without Warning

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18240 
====================================================================== 
Reported By:                leobrown
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18240
Category:                   Applications/app_voicemail
Reproducibility:            have not tried
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-11-02 06:46 CDT
Last Modified:              2010-11-02 09:37 CDT
====================================================================== 
Summary:                    VoicemailMain Exits Without Warning
Description: 
Hi

I've seen problems with VoicemailMain crashing in the past, from not being
able to lock paths, open audio files etc.

However, I have a VoiceMailMain which is opening a mailbox, but existing
after verifying a correct password.

The console trace is below, but because Asterisk is not crashing, I can
not provide a backtrace. Could you please give me some guidance on how to
further debug, as debug level 10 (shown below) only shows it
locking/unlocking paths and then exiting.

I have checked all permissions and even removed mailboxes and let Asterisk
create the paths itself. Voicemail() works fine, but VoicemailMain does
not. The relevant entry from voicemail.conf is also

Leo
====================================================================== 

---------------------------------------------------------------------- 
 (0128558) lmadsen (administrator) - 2010-11-02 09:37
 https://issues.asterisk.org/view.php?id=18240#c128558 
---------------------------------------------------------------------- 
You can produce a backtrace still by attaching to the existing process (per
Google:
http://gcc.gnu.org/onlinedocs/gnat_ugn_unw/Attaching-to-a-Running-Process.html)


You should also provide 'core show locks' as well, which will require you
to have Compiler Flags -> DEBUG_THREADS enabled.


~~~~~~~~~~~~~~~~~~~~~~~

Thank you for your bug report. In order to move your issue forward, we
require a backtrace from the core file produced after the crash. Please see
the doc/backtrace.txt file in your Asterisk source directory.

Also, be sure you have DONT_OPTIMIZE enabled in menuselect within the
Compiler Flags section, then:

make install

after enabling, reproduce the crash, and then execute the instructions in
doc/backtrace.txt.

When complete, attach that file to this issue report. Thanks!


~~~~~~~~~~~~~~~~~~~~~~~~~~
Debugging deadlocks:

Please select DEBUG_THREADS and DONT_OPTIMIZE in the Compiler Flags
section of menuselect. Recompile and install Asterisk (i.e. make install)

This will then give you the console command:

core show locks 

When the symptoms of the deadlock present themselves again, please provide
output of the deadlock via:

# asterisk -rx "core show locks" | tee /tmp/core-show-locks.txt

# gdb -se "asterisk" <pid of asterisk> | tee /tmp/backtrace.txt

gdb> bt
gdb> bt full
gdb> thread apply all bt

Then attach the core-show-locks.txt and backtrace.txt files to this issue.
Thanks! 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-11-02 09:37 lmadsen        Note Added: 0128558                          
======================================================================