Attachment 572868 Details for Bug 789162 – A copy-paste log of the gdb command, after today's update.

A copy-paste log of the gdb command, after today's update.

GDB log (after update today).txt (text/plain), 3.42 KB, created by Volans on 2012-03-26 20:51:29 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Volans

Created: 2012-03-26 20:51:29 UTC

Size: 3.42 KB

patch

obsolete

>[Volans@localhost ~]$ su
>Senha: 
>[root@localhost Volans]# cls
>bash: cls: command not found...
>clear[root@localhost Volans]# clear
>
>[root@localhost Volans]# gdb evolution --ex "b message_list_set_threaded" --ex r --ex c --ex c
>GNU gdb (GDB) Fedora (7.3.50.20110722-10.fc16)
>Copyright (C) 2011 Free Software Foundation, Inc.
>License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
>This is free software: you are free to change and redistribute it.
>There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
>and "show warranty" for details.
>This GDB was configured as "x86_64-redhat-linux-gnu".
>For bug reporting instructions, please see:
><http://www.gnu.org/software/gdb/bugs/>...
>Reading symbols from /usr/bin/evolution...(no debugging symbols found)...done.
>Function "message_list_set_threaded" not defined.
>Make breakpoint pending on future shared library load? (y or [n]) y
>
>Breakpoint 1 (message_list_set_threaded) pending.
>Starting program: /usr/bin/evolution 
>[Thread debugging using libthread_db enabled]
>Using host libthread_db library "/lib64/libthread_db.so.1".
>[New Thread 0x7ffff0616700 (LWP 2460)]
>Gkr-Message: couldn't connect to dbus session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
>
>(evolution:2457): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
>Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
>Erro GConf: O daemon D-BUS nÃ£o se encontra em execuÃ§Ã£o
>
>
>(evolution:2457): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
>Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
>
>** (evolution:2457): WARNING **: O daemon D-BUS nÃ£o se encontra em execuÃ§Ã£o
>
>
>(evolution:2457): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
>Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
>
>** (evolution:2457): WARNING **: O daemon D-BUS nÃ£o se encontra em execuÃ§Ã£o
>
>
>(evolution:2457): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
>Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
>
>(evolution:2457): evolution-shell-WARNING **: O daemon D-BUS nÃ£o se encontra em execuÃ§Ã£o
>
>
>(evolution:2457): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
>Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
>
>(evolution:2457): evolution-shell-WARNING **: O daemon D-BUS nÃ£o se encontra em execuÃ§Ã£o
>
>[New Thread 0x7fffefe00700 (LWP 2461)]
>
>** ERROR **: A ligaÃ§Ã£o estÃ¡ fechada
>
>Program received signal SIGTRAP, Trace/breakpoint trap.
>0x0000003c60e4d313 in g_logv () from /lib64/libglib-2.0.so.0
>Continuing.
>

Actions: View

Attachments on bug 789162: 572103 | 572106 | 572868