[asterisk-bugs] [Asterisk 0016734]: Core Dump on Exit - v1.6.2/FreeBSD

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16734 
====================================================================== 
Reported By:                ahhyes
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16734
Category:                   Core/Portability
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.2.1 
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-01-29 23:17 CST
Last Modified:              2010-02-03 18:39 CST
====================================================================== 
Summary:                    Core Dump on Exit - v1.6.2/FreeBSD
Description: 
Hi Guys,

I am running Asterisk 1.6.2.1 On FreeBSD 8 64 bit.
I have compiled and installed the application, and it appears to very
well, however upon exit (core stop gracefully), it seg faults and a core
dump file is created.

I have provided a back trace from gdb. 

Any ideas?

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

---------------------------------------------------------------------- 
 (0117683) lmadsen (administrator) - 2010-02-03 18:39
 https://issues.asterisk.org/view.php?id=16734#c117683 
---------------------------------------------------------------------- 
You're likely best to ask your programming question in #asterisk-dev on the
Freenode IRC network or the asterisk-dev mailing list (I'm unable to answer
it).

As there has been no developer assigned to this issue currently, I'd
suggest trying to gather as much information as you can via valgrind and
the other tools to provide as much information to a developer as possible.
Once this issue is assigned to someone, they may require access to a VM
demonstrating the issues if the information is insufficient to determine
the issue.

For now I'd use the #asterisk-dev chat or asterisk-dev mailing lists to
help gather the information required to debug the issue. Sorry I can't be
of any more assistance. Thanks! 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-02-03 18:39 lmadsen        Note Added: 0117683                          
======================================================================