[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 16:31 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?

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

---------------------------------------------------------------------- 
 (0117670) lmadsen (administrator) - 2010-02-03 16:31
 https://issues.asterisk.org/view.php?id=16734#c117670 
---------------------------------------------------------------------- 
The problem is Tilghman states that there is no valgrind or timerfd on
FreeBSD, so it's difficult to get information since your backtrace isn't
really usable. It kind of appears to me to be a memory corruption issue
(which would be debugged via valgrind... but.... it being FreeBSD).

I don't use FreeBSD at all, and will be unable to reproduce this issue
myself. If you're able to provide access to the system to a developer, they
may be able to move the issue forward, but there isn't anything I can do
further here.

I'm not a developer, so I'm not sure what else to ask for here. Any
additional information you feel may be useful you're welcome to attach to
the issue though. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-02-03 16:31 lmadsen        Note Added: 0117670                          
======================================================================