Re: [Ekiga-devel-list] Real Issue is Opal::Call virtual table missing

Good. I did  "print *call" in gdb. I will send results tmw.

On Tuesday, January 8, 2013, Eugen Dedu wrote:
I think Julien wants that in gdb when the crash appears you type
p call
or other command to see what is the type of the variable call.  Probably it is initialised (?) to another value, and he wants to see what is the type of this value in order to see where this is done.

Another possibility is to track changes to this variable, but I do not know gdb so well to know if possible and how to do it.

On 09/01/13 00:16, Lorin Melander wrote:
It is in the /ekiga/plugins/libnotify/libnotify-main.cpp
static void
call_notification_action_cb (NotifyNotification *notification,
                              gchar *action,
                              gpointer data)

Ekiga::Call *call = (Ekiga::Call *) data;<---- is this you want to know ?
call->answer ();

On Tue, Jan 8, 2013 at 2:13 PM, Julien Puydt<jpuydt free fr>  wrote:
Le 08/01/2013 21:27, Lorin Melander a écrit :

Two methods  call->answer() and call->hungup()

Right, two methods.

What is the type of the "call" object?

ekiga-devel-list mailing list
ekiga-devel-list gnome org


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]