Bug 16857 - Crash after an error trying to enable video fails
Summary: Crash after an error trying to enable video fails
Status: RESOLVED NOTOURBUG
Alias: None
Product: Telepathy
Classification: Unclassified
Component: rakia (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Mikhail Zabaluev
QA Contact: Telepathy bugs list
URL: https://sourceforge.net/tracker/index...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-25 18:14 UTC by Olivier Crête
Modified: 2008-08-04 06:37 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Olivier Crête 2008-07-25 18:14:55 UTC
Using tp-sofiasip darcs HEAD as of 25-Jul-2008 and sofia-sip 1.12.9 (and an experimental version of stream-engine for farsight2)

I call my PC from an N810 with diablo. A voice-only call is established.

Then I try to enable video from the N810.. The call is closed (by the n810)... Then it crashes.. and obviously now that I want to file a bug, I can't reproduce it to get a nice clean log...


#0  outgoing_other_destinations (orq=<value optimized out>) at nta.c:9186
	sr = (struct sipdns_resolver *) 0x63696d73
#1  0xb7e4b2b0 in outgoing_tport_error (agent=0x807b7e0, orq=0x8087890, tp=0x8087618, msg=0x8090f68, 
    error=110) at nta.c:7642
	tpn = (const tp_name_t *) 0x808765c
	__PRETTY_FUNCTION__ = "outgoing_tport_error"
#2  0xb7eb9d07 in tport_pending_error (self=0x8087618, dst=0x0, error=110) at tport.c:4187
	i = 0
	reported = 1
	callbacks = 0
	pending = (tport_pending_t *) 0x80938e0
	msg = (msg_t *) 0x8090f68
	__PRETTY_FUNCTION__ = "tport_pending_error"
#3  0xb7ec06ea in tport_error_report (self=0x8087618, errcode=110, addr=0x0) at tport.c:2521
	errmsg = 0xb7a54225 "Connection timed out"
	__func__ = "tport_error_report"
#4  0xb7ec083e in tport_error_event (self=0x8087618) at tport.c:4046
	errcode = <value optimized out>
	name = {{su_dummy = 0, su_family = 0, su_array = '\0' <repeats 31 times>, su_array16 = {
      0 <repeats 16 times>}, su_array32 = {0, 0, 0, 0, 0, 0, 0, 0}, su_sa = {sa_family = 0, 
      sa_data = '\0' <repeats 13 times>}, su_sin = {sin_family = 0, sin_port = 0, sin_addr = {s_addr = 0}, 
      sin_zero = "\000\000\000\000\000\000\000"}, su_sin6 = {sin6_family = 0, sin6_port = 0, 
      sin6_flowinfo = 0, sin6_addr = {in6_u = {u6_addr8 = '\0' <repeats 15 times>, u6_addr16 = {0, 0, 0, 0, 
            0, 0, 0, 0}, u6_addr32 = {0, 0, 0, 0}}}, sin6_scope_id = 0}}}
#5  0xb7ec262f in tport_connected (magic=0x8073810, w=0x808e690, self=0x8087618) at tport.c:2667
	events = 24
	mr = (tport_master_t *) 0x807ca58
	wait = {{fd = -1, events = 0, revents = 0}}
	error = <value optimized out>
	__PRETTY_FUNCTION__ = "tport_connected"
#6  0xb7f0faf3 in su_source_dispatch (gs=0x806fcb0, callback=0, user_data=0x0) at su_source.c:492
	root = <value optimized out>
	i = 16
	waits = <value optimized out>
	n = 18
	version = 20
	self = (su_port_t *) 0x806fce4
	__func__ = "su_source_dispatch"
#7  0xb7b9c04b in g_main_context_dispatch (context=0x806ec08) at gmain.c:2003
No locals.
#8  0xb7b9f5bf in g_main_context_iterate (context=0x806ec08, block=1, dispatch=1, self=0x806cd68)
    at gmain.c:2636
	got_ownership = <value optimized out>
	max_priority = 2147483647
	timeout = 1000
	some_ready = 1
	nfds = <value optimized out>
	allocated_nfds = <value optimized out>
	fds = (GPollFD *) 0x80b3570
	__PRETTY_FUNCTION__ = "g_main_context_iterate"
#9  0xb7b9f977 in g_main_loop_run (loop=0x806cfe0) at gmain.c:2844
	got_ownership = 0
	self = (GThread *) 0x806cd68
	__PRETTY_FUNCTION__ = "g_main_loop_run"
#10 0xb7b41510 in tp_run_connection_manager (prog_name=0x80624f5 "telepathy-sofiasip", 
    version=0x8062bb4 "0.5.10.1", construct_cm=0x804f5b0 <construct_cm>, argc=1, argv=0xbfefa5e4)
    at run.c:263
	fatal_mask = <value optimized out>
	connection = <value optimized out>
#11 0x0804f579 in main (argc=1, argv=0xbfefa5e4) at telepathy-sofiasip.c:154
	status = 1667853683
Comment 1 Mikhail Zabaluev 2008-08-04 06:37:33 UTC
Filed as Sofia-SIP sf.net #2037585


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.