Mercurial > pidgin
view libpurple/purple-send @ 25329:36897ddd3e08
This should prevent the crash in #8109 by stopping an invalid message from
getting in the queue. There is still a problem farther up from here in that
an invalid message shouldn't get this far - hopefully this will help track it
down by providing a message at the time the issue happens instead of crashing
later. Fixes #8109.
author | Daniel Atallah <daniel.atallah@gmail.com> |
---|---|
date | Thu, 15 Jan 2009 03:54:58 +0000 |
parents | 942bf314fc8a |
children | cea56d000b16 |
line wrap: on
line source
#!/bin/sh METHOD_NAME=$1 if test -z "$METHOD_NAME" then cat <<EOF This program calls purple API functions using DBus and prints the return value. If you are not interested in the return value, use purple-send-async. 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 PurpleAccountsFindConnected string: string:prpl-jabber $0 PurpleAccountsGetAll $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 --print-reply --type=method_call /im/pidgin/purple/PurpleObject im.pidgin.purple.PurpleInterface.$METHOD_NAME "$@" echo