[asterisk-bugs] [Asterisk 0014195]: Crash after - Remote peer reported an error, trying to establish the call anyway

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14195 
====================================================================== 
Reported By:                visu
Assigned To:                phsultan
====================================================================== 
Project:                    Asterisk
Issue ID:                   14195
Category:                   Channels/chan_gtalk
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-01-07 22:39 CST
Last Modified:              2009-01-15 11:39 CST
====================================================================== 
Summary:                    Crash after - Remote peer reported an error, trying
to establish the call anyway
Description: 
Asterisk always crashes after 

chan_gtalk.c: Remote peer reported an error, trying to establish the call
anyway

Visu



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

---------------------------------------------------------------------- 
 (0097932) phsultan (manager) - 2009-01-15 11:39
 http://bugs.digium.com/view.php?id=14195#c97932 
---------------------------------------------------------------------- 
First launch Asterisk with option -g in order to get a core file when
Asterisk crashes, ex :
#asterisk -vvvvg

When Asterisk happen to crash, a core file is dumped under /tmp, with a
name like /tmp/core.XXXXX. If multiple files are present, beware to point
to the correct file in the next step.

Open the core file with gdb :
#gdb asterisk /tmp/core.XXXXX

Store the output of the following command (under gdb) :
bt full

Attach the corresponding file to this ticket, do not post it as a note
please.

You'll have more information about how to get a backtrace in the
doc/backtrace.txt file. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-15 11:39 phsultan       Note Added: 0097932                          
======================================================================