Bug 24194 - can attempt to stat() a NULL .profile filename
Summary: can attempt to stat() a NULL .profile filename
Status: RESOLVED WONTFIX
Alias: None
Product: Telepathy
Classification: Unclassified
Component: mission-control (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-28 04:33 UTC by Simon McVittie
Modified: 2011-04-19 04:33 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Simon McVittie 2009-09-28 04:33:59 UTC
==4332== Syscall param stat64(file_name) points to 
              unaddressable byte(s)
==4332==    at 0x4F55188: _xstat (in /lib/libc-2.5.so)
==4332==    by 0x42509FF: _mc_profile_new (in /usr/lib/libmcclient.so.6.4.0)
==4332==    by 0x4250F73: mc_profile_lookup (in /usr/lib/libmcclient.so.6.4.0)
==4332==    by 0x417161A: (within /usr/lib/libosso-abook-1.0.so.0.0.0)
==4332==    by 0x4171763: (within /usr/lib/libosso-abook-1.0.so.0.0.0)
==4332==    by 0x424A1C5: account_ready_cb (in /usr/lib/libmcclient.so.6.4.0)
==4332==    by 0x4243B67: call_when_all_ready_cb (in /usr/lib/libmcclient.so.6.4.0)
==4332==    by 0x424414E: properties_get_all_cb (in /usr/lib/libmcclient.so.6.4.0)
==4332==    by 0x43CF951: tp_cli_dbus_properties_invoke_callback_get_all 
              (tp-cli-generic-body.h:1421)
==4332==    by 0x43D1C18: tp_proxy_pending_call_idle_invoke (proxy-methods.c:153)
==4332==    by 0x4E080E2: g_idle_dispatch (gmain.c:3966)
==4332==    by 0x4E09E3B: g_main_context_dispatch (gmain.c:1836)
==4332==    by 0x4E0D3C4: g_main_context_iterate (gmain.c:2467)
==4332==    by 0x4E0D6B7: g_main_loop_run (gmain.c:2675)
==4332==    by 0x4516B48: gtk_main (gtkmain.c:1200)
==4332==    by 0x8066CD6: main (messaging.c:214)
==4332==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
Comment 1 Simon McVittie 2011-04-19 04:33:19 UTC
All of libmcclient is WONTFIX, it'll be removed for Bug #24913.


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.