Valgrind reports with D-Bus API

Marcel Holtmann marcel at holtmann.org
Tue Jan 5 21:43:11 EST 2010


Hi guys,

so when running wpa_supplicant via valgrind, I get a lot of annoying
reports like this:

==25940== Invalid write of size 1
==25940==    at 0x43C30E: send_prop_changed_signal (dbus_new_helpers.c:622)
==25940==    by 0x43C507: wpa_dbus_flush_object_changed_properties (dbus_new_helpers.c:777)
==25940==    by 0x40CB5D: eloop_run (eloop.c:540)
==25940==    by 0x445307: wpa_supplicant_run (wpa_supplicant.c:2345)
==25940==    by 0x44D40F: main (main.c:274)
==25940==  Address 0x4cbd191 is 0 bytes after a block of size 1 alloc'd
==25940==    at 0x4A04481: calloc (vg_replace_malloc.c:418)
==25940==    by 0x43D3A5: wpas_dbus_register (dbus_new.c:817)
==25940==    by 0x43D797: wpas_dbus_register_interface (dbus_new.c:1510)
==25940==    by 0x409DDF: wpas_notify_iface_added (notify.c:55)
==25940==    by 0x447FC4: wpa_supplicant_add_iface (wpa_supplicant.c:2145)
==25940==    by 0x43AE5C: wpas_dbus_global_add_interface (dbus_old_handlers.c:174)
==25940==    by 0x4384BB: wpas_message_handler (dbus_old.c:341)
==25940==    by 0x3924C1CBED: _dbus_object_tree_dispatch_and_unlock (dbus-object-tree.c:856)
==25940==    by 0x3924C10A1B: dbus_connection_dispatch (dbus-connection.c:4485)
==25940==    by 0x442E37: dispatch_data (dbus_common.c:43)
==25940==    by 0x44332B: process_watch (dbus_common.c:79)
==25940==    by 0x40C53A: eloop_sock_table_dispatch (eloop.c:216)
==25940== 
==25940== Invalid write of size 1
==25940==    at 0x43C1C9: wpa_dbus_mark_property_changed (dbus_new_helpers.c:819)
==25940==    by 0x44965D: wpa_supplicant_event_scan_results (events.c:786)
==25940==    by 0x44AA97: wpa_supplicant_event (events.c:1466)
==25940==    by 0x4556D9: send_scan_event (driver_nl80211.c:755)
==25940==    by 0x457904: process_event (driver_nl80211.c:794)
==25940==    by 0x392001C4E3: nl_recvmsgs (nl.c:724)
==25940==    by 0x4521A7: wpa_driver_nl80211_event_receive (driver_nl80211.c:869)
==25940==    by 0x40C53A: eloop_sock_table_dispatch (eloop.c:216)
==25940==    by 0x40CB78: eloop_run (eloop.c:548)
==25940==    by 0x445307: wpa_supplicant_run (wpa_supplicant.c:2345)
==25940==    by 0x44D40F: main (main.c:274)
==25940==  Address 0x4cbd192 is 1 bytes after a block of size 1 alloc'd
==25940==    at 0x4A04481: calloc (vg_replace_malloc.c:418)
==25940==    by 0x43D3A5: wpas_dbus_register (dbus_new.c:817)
==25940==    by 0x43D797: wpas_dbus_register_interface (dbus_new.c:1510)
==25940==    by 0x409DDF: wpas_notify_iface_added (notify.c:55)
==25940==    by 0x447FC4: wpa_supplicant_add_iface (wpa_supplicant.c:2145)
==25940==    by 0x43AE5C: wpas_dbus_global_add_interface (dbus_old_handlers.c:174)
==25940==    by 0x4384BB: wpas_message_handler (dbus_old.c:341)
==25940==    by 0x3924C1CBED: _dbus_object_tree_dispatch_and_unlock (dbus-object-tree.c:856)
==25940==    by 0x3924C10A1B: dbus_connection_dispatch (dbus-connection.c:4485)
==25940==    by 0x442E37: dispatch_data (dbus_common.c:43)
==25940==    by 0x44332B: process_watch (dbus_common.c:79)
==25940==    by 0x40C53A: eloop_sock_table_dispatch (eloop.c:216)

Regards

Marcel




More information about the HostAP mailing list