Closed
Bug 740254
Opened 12 years ago
Closed 12 years ago
webrtc/signaling code access violation in timers_using_select code
Categories
(Core :: WebRTC: Signaling, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 794240
People
(Reporter: ehugg, Unassigned)
Details
(Whiteboard: [WebRTC], [blocking-webrtc-])
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20100101 Firefox/11.0 Build ID: 20120312181643 Steps to reproduce: Seg fault message below. I suspect the same problem is also in cpr_darwin_timers_using_select.c Wrote 1 bytes to socket 1 Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fff837fc700 (LWP 23184)] start_timer_service_loop () at ../../../../../media/webrtc/signaling/src/sipcc/cpr/linux/cpr_linux_timers_using_select.c:1248 1248 (void) read_timer_cmd(); (gdb) where #0 start_timer_service_loop () at ../../../../../media/webrtc/signaling/src/sipcc/cpr/linux/cpr_linux_timers_using_select.c:1248 #1 timerThread (data=<optimized out>) at ../../../../../media/webrtc/signaling/src/sipcc/cpr/linux/cpr_linux_timers_using_select.c:1013 #2 0x0000003151a07b41 in start_thread (arg=0x7fff837fc700) at pthread_create.c:305 #3 0x00000031516e0e6d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115
Reporter | ||
Updated•12 years ago
|
OS: Mac OS X → Linux
Hardware: x86 → x86_64
Updated•12 years ago
|
QA Contact: jsmith
Updated•12 years ago
|
Whiteboard: [WebRTC], [blocking-webrtc-]
Reporter | ||
Comment 1•12 years ago
|
||
This timer implementation is currently stubbed out in the OSX version darwin_timers_using_select. The resolution to this could be to remove this timer code for all platforms. static cprRC_t addTimerToList (cpr_timer_t *cprTimerPtr, uint32_t duration, void *data) { // TODO(ekr@rtfm.com): Put this back in when you figure out why it causes crashes return CPR_SUCCESS; #if 0
Reporter | ||
Comment 2•12 years ago
|
||
This was fixed by jib in Bug 794240
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•