A crash is never working as intended, so I'd say file a bug report
please [1]. Be sure to get a backtrace [2] and attach it to the issue.
A debug Asterisk log [3] at startup could be helpful as well.
[1] https://issues.asterisk.org/
[2] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace
[3]
https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information
Thanks!
--
Kevin Harwell
Digium - A Sangoma Company | Senior Software Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - US
Check us out at: https://digium.com & https://asterisk.org
I will.
At a glance, I don't see how this is possible with res_config_sqlite3
from Asterisk 13. When you create an issue, please attach the
res_config_sqlite3.conf file you are using.
Kind regards,
Sean
I found four different ways to crash Asterisk 13 with
res_config_sqlite3, just playing with config files. I must be lucky.
Bumped into a kernel bug today too. Maybe I should buy some lottery
tickets on my way home.
--
Dennis Buteyn
Xorcom Ltd
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
