[asterisk-bugs] [Asterisk 0011291]: Latest MySQL CDR crash on start
noreply at bugs.digium.com
noreply at bugs.digium.com
Wed Nov 21 23:38:16 CST 2007
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=11291
======================================================================
Reported By: IgorG
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 11291
Category: Addons/cdr_addon_mysql
Reproducibility: always
Severity: crash
Priority: normal
Status: feedback
Asterisk Version: SVN
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 89399
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 11-19-2007 03:52 CST
Last Modified: 11-21-2007 23:38 CST
======================================================================
Summary: Latest MySQL CDR crash on start
Description:
Latest MySQL CDR crash on start, if add noload to modules.conf all is OK.
Back trace attached.
======================================================================
----------------------------------------------------------------------
IgorG - 11-21-07 23:38
----------------------------------------------------------------------
I have repeated it again.
Tooday I've upgraded to latest trunk:
1. run 'make' and 'make clean' in both folders
2. run 'svn update'
3. then run ./configure --enable-dev-mode
4. Select modules as needed, then compile asterisk and install
5. Compile and install addons
I think that this is right sequence, but I have crash on loading
cdr_mysql. Commenting one line in utils.c prevent it from crash. Running
with valgrind give amazing results:
==10153== More than 1000 different errors detected. I'm not reporting any
more.
==10153== Final error counts will be inaccurate. Go fix your program!
==10153== Rerun with --error-limit=no to disable this cutoff. Note
==10153== that errors may occur in your program without prior warning
from
==10153== Valgrind, because errors are no longer being displayed.
Issue History
Date Modified Username Field Change
======================================================================
11-21-07 23:38 IgorG Note Added: 0074172
======================================================================
More information about the asterisk-bugs
mailing list