Hi,
On Tue, Jan 12, 2010, Zhu Yanhai wrote:
> --- a/audio/telephony-ofono.c
> +++ b/audio/telephony-ofono.c
> @@ -574,12 +574,20 @@ static void list_modem_reply(DBusPendingCall *call, void *user_data)
> while (dbus_message_iter_get_arg_type(&sub) != DBUS_TYPE_INVALID) {
>
> dbus_message_iter_get_basic(&sub, &modem_obj_path_local);
> + if (modem_obj_path_local == NULL)
> + continue;
dbus_message_iter_get_basic doesn't set the pointer to NULL in the case
of failure, so this check is useless. The D-Bus documentation says the
following about dbus_message_iter_get_basic:
"Be sure you have somehow checked that dbus_message_iter_get_arg_type()
matches the type you are expecting, or you'll crash when you try to use
an integer as a string or something."
You could either change the while loop condition from
"!= DBUS_TYPE_INVALID" to "== DBUS_TYPE_STRING", or if you just want to
pick the first modem in the list (which probably makes more sense than
the current method of picking the last one and leaking the path to every
modem before it) remove the loop completely and then bail out (goto
done) if the first parameter isn't a string.
In the future, please check the reference documentation instead of
guessing the usage of the API. You can find it e.g. here:
http://dbus.freedesktop.org/doc/api/html/group__DBus.html
> modem_obj_path = g_strdup(modem_obj_path_local);
> - debug("modem_obj_path is %p, %s\n", modem_obj_path,
> + debug("modem_obj_path is %p, %s", modem_obj_path,
> modem_obj_path);
The removal of the unnecessary newline character is good, but there are
a few other issues that are strange with this:
1. What's the value of printing the memory address of the string here?
2. Leaking modem_obj_path if it was already set
Since there are a few different issues to fix here, feel free to split
them up into separate patches (e.g. the summary of the commit message
isn't accurate anymore).
Johan
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
