Summary:ASTERISK-08669: Dumps core at usecount, module format_mp3
Reporter:Wei (wcjiang)Labels:
Date Opened:2007-01-27 13:57:51.000-0600Date Closed:2007-02-16 14:22:39.000-0600
Versions:Frequency of
Environment:Attachments:( 0) crash.backtrace
( 1) crash.backtrace2
Description:Output from running gdb /usr/sbin/asterisk core.28666:

#0  0x00362e65 in usecount () from /usr/lib/asterisk/modules/format_mp3.so
(gdb) next
The program is not being run.
(gdb) list
1992                    } else if (!strcasecmp(v->name, "rungroup")) {
1993                            ast_copy_string(ast_config_AST_RUN_GROUP, v->value, sizeof(ast_config_AST_RUN_GROUP));
1994                    }
1995                    v = v->next;
1996            }
1997            ast_config_destroy(cfg);
1998    }
2000    int main(int argc, char *argv[])
2001    {


I downloaded asterisk-1.2.14.tar.gz from asterisk.org on 1/15 and asterisk-addons-1.2.5.tar.gz on 1/19 and installed them on linux kernel 2.6.18-1.2257.fc5. It works fine most of the time but crashed twice yesterday at the same function. There were only a couple of callers on the system at the time, one caller said it sounded like she was put on hold (but she wasn't).

Core file available on request.
Comments:By: Tilghman Lesher (tilghman) 2007-01-27 23:21:35.000-0600

For any crash, I need a stack backtrace generated from the core file.  Please read doc/README.backtrace.

By: Wei (wcjiang) 2007-01-28 12:55:02.000-0600

Crashed again at the same function when I ran asterisk -rx 'stop gracefully', second backtrace uploaded

By: Tilghman Lesher (tilghman) 2007-01-28 21:16:36.000-0600

Please recompile with "make clean dont-optimize" so we can get better debugging information from the backtrace.

By: Joshua C. Colp (jcolp) 2007-02-15 20:15:12.000-0600

Any luck with the unoptimized backtraces?

By: Wei (wcjiang) 2007-02-15 20:21:33.000-0600

Since it is a production system I decided to roll back to 1.2.4 and have not had a crash since.

By: Joshua C. Colp (jcolp) 2007-02-16 14:22:39.000-0600

Okay since I've been unable to reproduce this and you've switched back I'll close this out for now. If you upgrade and still have this issue feel free to reopen with the needed information. Peace!