On Tue, Mar 17, 2009 at 7:32 AM, Szymon Olko <solko@gcdf.pl> wrote:

Anthony Minessale pisze:

> if you can reproduce the steps to get it in that state, go into another
> console on the same box and do the following:
>
> 1) cd to the FS source dir
>
> 2) sh scripts/freeswitch-gcore > core.trace
>
> 3) attach core.trace to a jira ticket
>
> http://jira.freeswitch.org
>
>

Today I found core dump from yesterday. I killed freeswitch with 'kill -9' so it produced core dump as I belive. Don't know if it
useful?

#0 0x0055d263 in strlen () from /lib/libc.so.6
(gdb) bt
#0 0x0055d263 in strlen () from /lib/libc.so.6
#1 0x0052d82e in vfprintf () from /lib/libc.so.6
#2 0x0054dc9c in vasprintf () from /lib/libc.so.6
#3 0x00c07a9b in switch_vasprintf (ret=0xb56123c4, fmt=0x915dd8 "Conference %s (%u member%s%s)\n", ap=0xb56123e8 "") at
src/switch_apr.c:917
#4 0x00c14e1b in switch_console_stream_write (handle=0xb5612958, fmt=0x915dd8 "Conference %s (%u member%s%s)\n") at
src/switch_console.c:125
#5 0x0090eae5 in conf_api_sub_list (conference=0xb7988b90, stream=0xb5612958, argc=1, argv=0xb5612478) at mod_conference.c:3100
#6 0x009106ba in conf_api_main (cmd=0x8539caf "list", session=0x0, stream=0xb5612958) at mod_conference.c:4019
#7 0x00c2f40d in switch_api_execute (cmd=0x8539ca4 "conference", arg=0x8539caf "list", session=0x0, stream=0xb5612958)
at src/switch_loadable_module.c:1541
#8 0x00bb16c2 in api_exec (thread=0x0, obj=0xb5612a08) at mod_event_socket.c:1280
#9 0x00bb2698 in parse_command (listener=0xb79f42a8, event=0xb5613390, reply=0xb5613123 "", reply_len=512) at mod_event_socket.c:1656
#10 0x00bb43d3 in listener_run (thread=0xb3aa1b88, obj=0xb79f42a8) at mod_event_socket.c:2055
#11 0x00c8b606 in dummy_worker (opaque=0xb3aa1b88) at threadproc/unix/thread.c:138
#12 0x0037745b in start_thread () from /lib/libpthread.so.0
#13 0x005bee5e in clone () from /lib/libc.so.6

>
> On Mon, Mar 16, 2009 at 4:45 AM, Szymon Olko <solko@gcdf.pl> wrote:
>
> Hi,
>
> Today I could do nothing in conference. When I opend fs_cli I could
> run 'status', and other commands, but when I input
> 'conference list' I did not receive any response. It happed also via
> event_socket. On fs_cli I saw such logs afters 'fsctl
> shutdown asap'
>
> freeswitch@internal> 2009-03-16 11:29:14 [DEBUG]
> mod_conference.c:5663 mod_conference_shutdown() Waiting for 3 threads
> 2009-03-16 11:29:14 [DEBUG] mod_conference.c:5663
> mod_conference_shutdown() Waiting for 3 threads
> 2009-03-16 11:29:14 [DEBUG] mod_conference.c:5663
> mod_conference_shutdown() Waiting for 3 threads
> 2009-03-16 11:29:14 [DEBUG] mod_conference.c:5663
> mod_conference_shutdown() Waiting for 3 threads
> 2009-03-16 11:29:14 [DEBUG] mod_conference.c:5663
> mod_conference_shutdown() Waiting for 3 threads
> 2009-03-16 11:29:15 [DEBUG] mod_conference.c:5663
> mod_conference_shutdown() Waiting for 3 threads
> 2009-03-16 11:29:15 [DEBUG] mod_conference.c:5663
> mod_conference_shutdown() Waiting for 3 threads
> 2009-03-16 11:29:15 [DEBUG] mod_conference.c:5663
> mod_conference_shutdown() Waiting for 3 threads
> 2009-03-16 11:29:15 [DEBUG] mod_conference.c:5663
> mod_conference_shutdown() Waiting for 3 threads
> 2009-03-16 11:29:15 [DEBUG] mod_conference.c:5663
> mod_conference_shutdown() Waiting for 3 threads
> 2009-03-16 11:29:15 [DEBUG] mod_conference.c:5663
> mod_conference_shutdown() Waiting for 3 threads
> 2009-03-16 11:29:15 [DEBUG] mod_conference.c:5663
> mod_conference_shutdown() Waiting for 3 threads
> 2009-03-16 11:29:15 [DEBUG] mod_conference.c:5663
> mod_conference_shutdown() Waiting for 3 threads
> 2009-03-16 11:29:15 [DEBUG] mod_conference.c:5663
> mod_conference_shutdown() Waiting for 3 threads
> 2009-03-16 11:29:15 [DEBUG] mod_conference.c:5663
> mod_conference_shutdown() Waiting for 3 threads
> 2009-03-16 11:29:16 [DEBUG] mod_conference.c:5663
> mod_conference_shutdown() Waiting for 3 threads
> 2009-03-16 11:29:16 [DEBUG] mod_conference.c:5663
> mod_conference_shutdown() Waiting for 3 threads
>
> How can I debug such situations to open usable ticket?
>
> _______________________________________________
> Freeswitch-dev mailing list
> Freeswitch-dev@lists.freeswitch.org

> <mailto:Freeswitch-dev@lists.freeswitch.org>

> http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev
> http://www.freeswitch.org
>
>
>
>
> --
> Anthony Minessale II
>
> FreeSWITCH http://www.freeswitch.org/
> ClueCon http://www.cluecon.com/
>
> AIM: anthm
> MSN:anthony_minessale@hotmail.com

> <mailto:MSN%3Aanthony_minessale@hotmail.com>

> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com

> <mailto:PAYPAL%3Aanthony.minessale@gmail.com>
> IRC: irc.freenode.net <http://irc.freenode.net> #freeswitch

>
> FreeSWITCH Developer Conference
> sip:888@conference.freeswitch.org

> <mailto:sip%3A888@conference.freeswitch.org>

> iax:guest@conference.freeswitch.org/888

> <http://iax:guest@conference.freeswitch.org/888>

> googletalk:conf+888@conference.freeswitch.org

> <mailto:googletalk%3Aconf%2B888@conference.freeswitch.org>
> pstn:213-799-1400
>
>
> ------------------------------------------------------------------------

>
> _______________________________________________
> Freeswitch-dev mailing list
> Freeswitch-dev@lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev
> http://www.freeswitch.org

_______________________________________________
Freeswitch-dev mailing list
Freeswitch-dev@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev
http://www.freeswitch.org