"Syscall param socketcall.sendmsg(msg.msg_iov[i]) points to uninitialised byte(s)"

Bug #953096 reported by Sebastien Bacher
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
DBus Menu
Confirmed
Medium
Unassigned
libdbusmenu (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Using libdbusmenu 0.5.93 with r384 backported:

==10300== Syscall param socketcall.sendmsg(msg.msg_iov[i]) points to uninitialised byte(s)
==10300== at 0x4D29F08: sendmsg (socket.S:100)
==10300== by 0x499DF75: write_message_continue_writing (gdbusprivate.c:1033)
==10300== by 0x499E4DF: continue_writing (gdbusprivate.c:1528)
==10300== by 0x499E592: continue_writing_in_idle_cb (gdbusprivate.c:1549)
==10300== by 0x4ABC7EF: g_idle_dispatch (gmain.c:4629)
==10300== by 0x4ABED89: g_main_context_dispatch (gmain.c:2510)
==10300== by 0x4ABF194: g_main_context_iterate.isra.21 (gmain.c:3118)
==10300== by 0x4ABF5DA: g_main_loop_run (gmain.c:3312)
==10300== by 0x4E2076D: clone (clone.S:130)
==10300== Address 0x11dd8515 is 405 bytes inside a block of size 1,024 alloc'd
==10300== at 0x402BF52: realloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
==10300== by 0x4AC47D2: standard_realloc (gmem.c:92)
==10300== by 0x4AC4FB8: g_realloc (gmem.c:224)
==10300== by 0x4920684: array_resize (gmemoryoutputstream.c:501)
==10300== by 0x4920F7A: g_memory_output_stream_write (gmemoryoutputstream.c:578)
==10300== by 0x4928CA5: g_output_stream_write (goutputstream.c:222)
==10300== by 0x49145AE: g_filter_output_stream_write (gfilteroutputstream.c:266)
==10300== by 0x4928CA5: g_output_stream_write (goutputstream.c:222)
==10300== by 0x4928E1F: g_output_stream_write_all (goutputstream.c:274)
==10300== by 0x48F5EF0: g_data_output_stream_put_byte (gdataoutputstream.c:230)
==10300== by 0x49906E6: append_value_to_blob (gdbusmessage.c:1906)
==10300== by 0x4990787: append_value_to_blob (gdbusmessage.c:2078)
==10300== by 0x498FF76: append_value_to_blob (gdbusmessage.c:2145)
==10300== by 0x4990049: append_value_to_blob (gdbusmessage.c:2120)
==10300== by 0x4990787: append_value_to_blob (gdbusmessage.c:2078)
==10300== by 0x4990049: append_value_to_blob (gdbusmessage.c:2120)
==10300== by 0x4990787: append_value_to_blob (gdbusmessage.c:2078)
==10300== by 0x499464D: g_dbus_message_to_blob (gdbusmessage.c:2200)
==10300== by 0x4987DC6: g_dbus_connection_send_message_unlocked (gdbusconnection.c:1608)
==10300== by 0x498B65A: g_dbus_connection_send_message (gdbusconnection.c:1713)
==10300== by 0x498F02E: g_dbus_connection_emit_signal (gdbusconnection.c:5146)
==10300== by 0x9345763: menuitem_property_idle (server.c:1032)
==10300== by 0x4ABC7EF: g_idle_dispatch (gmain.c:4629)
==10300== by 0x4ABED89: g_main_context_dispatch (gmain.c:2510)
==10300== by 0x4ABF194: g_main_context_iterate.isra.21 (gmain.c:3118)
==10300== by 0x4ABF270: g_main_context_iteration (gmain.c:3179)
==10300== by 0x49631A3: g_application_run (gapplication.c:1496)
==10300== by 0x8067867: main (nautilus-main.c:101)

Revision history for this message
Sebastien Bacher (seb128) wrote :

Oh, that's running current nautilus in precise under valgrind

David Barth (dbarth)
Changed in libdbusmenu (Ubuntu):
importance: Undecided → Medium
Changed in dbusmenu:
importance: Undecided → Medium
Changed in libdbusmenu (Ubuntu):
status: New → Triaged
Changed in dbusmenu:
status: New → Triaged
status: Triaged → Confirmed
Changed in libdbusmenu (Ubuntu):
status: Triaged → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.