Summary: | Seg fault running test-callable-example | ||
---|---|---|---|
Product: | Telepathy | Reporter: | Ken VanDine <ken.vandine> |
Component: | tp-glib | Assignee: | Simon McVittie <smcv> |
Status: | RESOLVED FIXED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
Severity: | blocker | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | Other | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
Valgrind log of the crash
this might work? Crash after applying the patch from the previous comment Additional patch: together, these are sufficient in sjoerd's build environment Simpler version of the previous patches |
Description
Ken VanDine
2009-06-09 13:36:53 UTC
Link to the ubuntu bug https://bugs.launchpad.net/ubuntu/+source/telepathy-glib/+bug/385358 Sjoerd is investigating. Created attachment 26716 [details]
Valgrind log of the crash
Created attachment 26718 [details] [review] this might work? I can't reproduce this (on Debian unstable i386 with an amd64 kernel, if that matters), which is strange... the valgrind log looks as though this ought to happen every time, if I'm right about the cause? Anyway, here's an attempt at fixing it blindly by reference to the valgrind log. Created attachment 26724 [details]
Crash after applying the patch from the previous comment
Created attachment 26725 [details] [review] Additional patch: together, these are sufficient in sjoerd's build environment Another instance of a similar problem. Together, these could be simplified to having example_callable_media_stream_close ref the stream until it returns, or even just having the emission of the REMOVED signal be the last thing in the function. I'm not sure which of these is best style, or why this worked reliably (and without use-after-free) for me... Created attachment 26726 [details] [review] Simpler version of the previous patches The two patches above work, but this one is simpler and seems more appropriate. Fixed in 0.7.32 |
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.