pidgin and VPN issues.

Richard Allen ra at ra.is
Wed May 15 07:16:30 EDT 2013


> Expect gdb backtraces the next time this happens :)

Got them.   And things look a bit diffrent:

#0  0x0000003b56c0e627 in __libc_send (fd=17, buf=0x1e2f2a0, n=427, flags=-1)
    at ../sysdeps/unix/sysv/linux/x86_64/send.c:32
#1  0x00000037b5225b8b in pt_Send () from /lib64/libnspr4.so
#2  0x00000037b5e1cd5c in ssl_DefSend () from /lib64/libssl3.so
#3  0x00000037b5e20e2e in ssl_SendSavedWriteData () from /lib64/libssl3.so
#4  0x00000037b5e22240 in ssl_SecureSend () from /lib64/libssl3.so
#5  0x00000037b5e26197 in ssl_Write () from /lib64/libssl3.so
#6  0x00007f0d6df57b57 in ssl_nss_write (gsc=<optimized out>, data=<optimized out>, len=<optimized out>)
    at ssl-nss.c:496
#7  0x00007f0d7132b294 in transport_write () from /usr/lib64/purple-2/libsipe.so
#8  0x00007f0d7132bade in sipe_backend_transport_flush () from /usr/lib64/purple-2/libsipe.so
#9  0x00007f0d71306230 in sipe_core_deallocate () from /usr/lib64/purple-2/libsipe.so
#10 0x00007f0d712f3dc2 in sipe_purple_close () from /usr/lib64/purple-2/libsipe.so
#11 0x0000003b6045fee6 in _purple_connection_destroy (gc=0x1fad8c0) at connection.c:275
#12 0x0000003b60446606 in purple_account_disconnect (account=account at entry=0x192ce90) at account.c:1284
#13 0x0000003b6045ebd5 in purple_connection_disconnect_cb (data=0x192ce90,
    data at entry=<error reading variable: value has been optimized out>) at connection.c:523
#14 0x0000003b58c485db in g_timeout_dispatch (source=source at entry=0x1b3d700, callback=<optimized out>,
    user_data=<optimized out>) at gmain.c:4026
#15 0x0000003b58c47a55 in g_main_dispatch (context=0x1494830) at gmain.c:2715
#16 g_main_context_dispatch (context=context at entry=0x1494830) at gmain.c:3219
#17 0x0000003b58c47d88 in g_main_context_iterate (context=0x1494830, block=block at entry=1,
    dispatch=dispatch at entry=1, self=<optimized out>) at gmain.c:3290
---Type <return> to continue, or q <return> to quit---
#18 0x0000003b58c48182 in g_main_loop_run (loop=0x1c3c7e0) at gmain.c:3484
#19 0x0000003b6ed4b077 in IA__gtk_main () at gtkmain.c:1257
#20 0x0000000000431491 in main (argc=1, argv=0x7fff65b7df38) at gtkmain.c:934


I did a few contiune's and ctrl+c's but always the same bt.

Step 0 lists fd 17:

[ra at hamburger ~]$ ll /proc/2863/fd/17
lrwx------. 1 ra ra 64 May 14 00:04 /proc/2863/fd/17 -> socket:[155804]


This time a socket which makes more sense.  the last time I checked what the fd was pidgin had already recovered so perhaps some fd's had been closed and reopened throwing off the numbers?

[ra at hamburger ~]$ kill 2863
[ra at hamburger ~]$ kill 2863
[ra at hamburger ~]$ kill 2863
[ra at hamburger ~]$ kill 2863
[ra at hamburger ~]$ kill 2863
[ra at hamburger ~]$ kill 2863
[ra at hamburger ~]$ kill 2863
[ra at hamburger ~]$ kill 2863
[ra at hamburger ~]$ kill 2863
[ra at hamburger ~]$ kill 2863
[ra at hamburger ~]$ kill -9 2863
[ra at hamburger ~]$ kill -9 2863
bash: kill: (2863) - No such process





More information about the Support mailing list