view libpurple/purple-send-async @ 31519:0c0b94fb9ac7

oscar: Fix a memleak on receipt of messages ==32109== 2,981 bytes in 7 blocks are definitely lost in loss record 18,095 of 18,342 ==32109== at 0x4C244E8: malloc (vg_replace_malloc.c:236) ==32109== by 0x90D8534: g_malloc (gmem.c:132) ==32109== by 0x1613A408: byte_stream_getstr (bstream.c:167) ==32109== by 0x161434B3: incomingim (family_icbm.c:928) ==32109== by 0x161440A4: snachandler (family_icbm.c:2112) ==32109== by 0x1614B4D2: flap_connection_recv (flap_connection.c:776)

#!/bin/sh

METHOD_NAME=$1

if test -z "$METHOD_NAME"
then
    cat <<EOF
This program calls purple API functions using DBus.  As opposed to purple-send,
it does not print the return value.

Usage:

   $0 method-name type1:parameter1 type2:parameter2 ...

This shell script just invokes dbus-send, see man dbus-send for how
to specify the parameters.

Examples:

   $0 PurpleCoreQuit

Use dbus-viewer to get the list of supported functions and their parameters.
EOF
    exit 1
fi

shift
dbus-send --dest=im.pidgin.purple.PurpleService --type=method_call /im/pidgin/purple/PurpleObject im.pidgin.purple.PurpleInterface.$METHOD_NAME "$@"