Ubuntu中文论坛

致力于Ubuntu中文推广
http://forum.ubuntu.com.cn/

新的qq插件 pidgin-lwqq 0.4.0 更新

http://forum.ubuntu.com.cn/viewtopic.php?t=382754

分页： 80 / 81

Re: 新的qq插件 pidgin-lwqq 0.4.0 更新

发表于 ： 2015-02-11 16:20
由 lainme
试试安装pidgin-dbg和开启了debug的pidgin-lwqq，然后再用gdb看一下。

Re: 新的qq插件 pidgin-lwqq 0.4.0 更新

发表于 ： 2015-02-11 16:30
由 newton1972
开启了debug的pidgin-lwqq, 编译时如何加参数

Re: 新的qq插件 pidgin-lwqq 0.4.0 更新

发表于 ： 2015-02-11 16:32
由 lainme
cmake .. -DCMAKE_BUILD_TYPE=Debug

Re: 新的qq插件 pidgin-lwqq 0.4.0 更新

发表于 ： 2015-02-11 16:50
由 newton1972
提示信息没有变化, 我编译参数用的不对吗
loongson@yeeloong:~$ gdb pidgin
GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 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 "mipsel-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/pidgin...Reading symbols from /usr/lib/debug/usr/bin/pidgin...done.
done.
(gdb) r
Starting program: /usr/bin/pidgin
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/mipsel-linux-gnu/libthread_db.so.1".
[New Thread 0x71167300 (LWP 20369)]
[New Thread 0x703ff300 (LWP 20372)]
[New Thread 0x6fbff300 (LWP 20373)]

Program received signal SIGSEGV, Segmentation fault.
0x00000000 in ?? ()
(gdb) bt
#0 0x00000000 in ?? ()
#1 0x00000000 in ?? ()
(gdb)

Re: 新的qq插件 pidgin-lwqq 0.4.0 更新

发表于 ： 2015-02-12 15:04
由 newton1972
重装了pidgin所有的包, 编译了带debug的lwqq, gdb输出信息还是不变. 下面是pidgin -d得到的一个新信息, 提示pidgin: malloc.c:4567出错, 应该有帮助:

(14:34:18) util: Writing file prefs.xml to directory /home/loongson/.purple
(14:34:18) util: Writing file /home/loongson/.purple/prefs.xml
(14:34:18) util: Writing file accounts.xml to directory /home/loongson/.purple
(14:34:18) util: Writing file /home/loongson/.purple/accounts.xml
(14:34:18) Session Management: Received first save_yourself
(14:34:18) Session Management: Received save_complete
(14:34:18) docklet: embedded
pidgin: malloc.c:4567: _int_malloc: Assertion `victim->fd_nextsize->bk_nextsize == victim' failed.
已放弃
loongson@yeeloong:~$

Re: 新的qq插件 pidgin-lwqq 0.4.0 更新

发表于 ： 2015-02-12 15:18
由 lainme
还是觉得这不像是pidgin-lwqq的错误，不知道你登录其它协议会不会有问题。只能等xihuc或其它懂的人了。

Re: 新的qq插件 pidgin-lwqq 0.4.0 更新

发表于 ： 2015-02-12 15:24
由 newton1972
不知道是pidgin的问题, 还是lwqq的问题, 还是其他问题?
我的系统是Debian7.8, 我的Pidgin版本是Pidgin 2.10.10 (libpurple 2.10.10)
Pidgin编译信息
Arguments to ./configure: '--build=mipsel-linux-gnu' '--prefix=/usr' '--includedir=${prefix}/include' '--mandir=${prefix}/share/man' '--infodir=${prefix}/share/info' '--sysconfdir=/etc' '--localstatedir=/var' '--libexecdir=${prefix}/lib/pidgin' '--disable-maintainer-mode' '--disable-dependency-tracking' '--disable-silent-rules' '--disable-gevolution' '--enable-cap' '--with-system-ssl-certs=/etc/ssl/certs' '--enable-perl' '--with-zephyr=/usr' '--enable-dbus' '--enable-gnutls=no' '--enable-nss=yes' '--enable-cyrus-sasl' '--enable-vv' '--enable-tcl' '--enable-tk' '--with-dynamic-prpls=bonjour,gg,irc,jabber,msn,myspace,mxit,novell,oscar,sametime,simple,yahoo,zephyr' '--enable-nm' 'build_alias=mipsel-linux-gnu' 'CFLAGS=-g -O2 -Wformat -Werror=format-security -Wall' 'LDFLAGS=-Wl,-z,relro -Wl,--as-needed' 'CPPFLAGS=-D_FORTIFY_SOURCE=2'
Print debugging messages: No
Plugins: Enabled
SSL: SSL support is present.

Library Support
Cyrus SASL: Enabled
D-Bus: Enabled
Evolution Addressbook: Disabled
Gadu-Gadu library (libgadu): Internal
GtkSpell: Enabled
GnuTLS: Disabled
GStreamer: Enabled
Mono: Disabled
NetworkManager: Enabled
Network Security Services (NSS): Enabled
Perl: Enabled
Tcl: Enabled
Tk: Enabled
UTF-8 DNS (IDN): Enabled
Voice and Video: Enabled
X Session Management: Enabled
XScreenSaver: Enabled
Zephyr library (libzephyr): External
Zephyr uses Kerberos: No

Re: 新的qq插件 pidgin-lwqq 0.4.0 更新

发表于 ： 2015-02-12 15:31
由 newton1972
谢谢lainme耐心指导, 让我学了很多新东西. 刚才有次正常登录, 但提示一个ERROR, 说浏览器发送一个无效的请求, 不知和登录困难是否有关
(15:15:11) docklet: embedded
Verify code: !VFJ
Get verify code OK
Verify code: !ALC
Get verify code OK
(15:15:13) util: Writing file blist.xml to directory /home/loongson/.purple
(15:15:13) util: Writing file /home/loongson/.purple/blist.xml
[Feb 12 15:15:16] ERROR[11331]: info.c:432 process_online_buddies:
unexpected response
http:400, response:
<html><body><h1>400 Bad request</h1>
Your browser sent an invalid request.
</body></html>

Re: 新的qq插件 pidgin-lwqq 0.4.0 更新

发表于 ： 2015-02-12 17:59
由 newton1972
终于有回溯了
(gdb) r
Starting program: /usr/bin/pidgin
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/mipsel-linux-gnu/libthread_db.so.1".
[New Thread 0x71167300 (LWP 3747)]
[New Thread 0x703ff300 (LWP 3750)]
[New Thread 0x6fbff300 (LWP 3751)]

Program received signal SIGSEGV, Segmentation fault.
0x7550ff18 in vp_func_p_i (func=0x3065416b, vp=0x49744333, q=0x63353930)
at /home/loongson/Desktop/GitHub/lwqq/lib/vplist.c:274
274 if(q) *(int*)q = ret;
(gdb) bt
#0 0x7550ff18 in vp_func_p_i (func=0x3065416b, vp=0x49744333, q=0x63353930)
at /home/loongson/Desktop/GitHub/lwqq/lib/vplist.c:274
#1 0x38795142 in ?? ()
Backtrace stopped: frame did not save the PC
(gdb)

Re: 新的qq插件 pidgin-lwqq 0.4.0 更新

发表于 ： 2015-02-12 20:04
由 newton1972
连续实验, 一共有3种信息, 第1种出现最多,超过3/4. 补充一下, 我用的是龙芯的8089d, mipsel架构, debian7.8, Pidgin2.10.10-1~deb7u1
No1

代码： 全选

(gdb) r
Starting program: /usr/bin/pidgin 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/mipsel-linux-gnu/libthread_db.so.1".
[New Thread 0x71167300 (LWP 4384)]
[New Thread 0x703ff300 (LWP 4387)]
[New Thread 0x6fbff300 (LWP 4388)]

Program received signal SIGSEGV, Segmentation fault.
0x7550ff18 in vp_func_p_i (func=0x54504f35, vp=0x654c7669, q=0x45384654)
    at /home/loongson/Desktop/GitHub/lwqq/lib/vplist.c:274
274		if(q) *(int*)q = ret;
(gdb) bt full
#0  0x7550ff18 in vp_func_p_i (func=0x54504f35, vp=0x654c7669, q=0x45384654)
    at /home/loongson/Desktop/GitHub/lwqq/lib/vplist.c:274
        p1 = 0x312a3333
        ret = 0
#1  0x30624c66 in ?? ()
No symbol table info available.
Backtrace stopped: frame did not save the PC
(gdb) q
No2

代码： 全选

(gdb) r
Starting program: /usr/bin/pidgin 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/mipsel-linux-gnu/libthread_db.so.1".
[New Thread 0x71167300 (LWP 6101)]
[New Thread 0x703ff300 (LWP 6104)]
[New Thread 0x6fbff300 (LWP 6105)]

Program received signal SIGSEGV, Segmentation fault.
0x7550ff18 in vp_func_p_i (func=0x73374a57, vp=0x32784464, q=0x32735256)
    at /home/loongson/Desktop/GitHub/lwqq/lib/vplist.c:274
274		if(q) *(int*)q = ret;
(gdb) bt
#0  0x7550ff18 in vp_func_p_i (func=0x73374a57, vp=0x32784464, q=0x32735256)
    at /home/loongson/Desktop/GitHub/lwqq/lib/vplist.c:274
#1  0x6f347330 in ?? ()
warning: GDB can't find the start of the function at 0x6f34732e.

    GDB is unable to find the start of the function at 0x6f34732e
and thus can't determine the size of that function's stack frame.
This means that GDB may be unable to access that stack frame, or
the frames below it.
    This problem is most likely caused by an invalid program counter or
stack pointer.
    However, if you think GDB should simply search farther back
from 0x6f34732e for code which looks like the beginning of a
function, you can increase the range of the search using the `set
heuristic-fence-post' command.
(gdb) q
No3

代码： 全选

(gdb) r
Starting program: /usr/bin/pidgin 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/mipsel-linux-gnu/libthread_db.so.1".
[New Thread 0x71167300 (LWP 6101)]
[New Thread 0x703ff300 (LWP 6104)]
[New Thread 0x6fbff300 (LWP 6105)]

Program received signal SIGSEGV, Segmentation fault.
0x7550ff18 in vp_func_p_i (func=0x73374a57, vp=0x32784464, q=0x32735256)
    at /home/loongson/Desktop/GitHub/lwqq/lib/vplist.c:274
274		if(q) *(int*)q = ret;
(gdb) bt
#0  0x7550ff18 in vp_func_p_i (func=0x73374a57, vp=0x32784464, q=0x32735256)
    at /home/loongson/Desktop/GitHub/lwqq/lib/vplist.c:274
#1  0x6f347330 in ?? ()
warning: GDB can't find the start of the function at 0x6f34732e.

    GDB is unable to find the start of the function at 0x6f34732e
and thus can't determine the size of that function's stack frame.
This means that GDB may be unable to access that stack frame, or
the frames below it.
    This problem is most likely caused by an invalid program counter or
stack pointer.
    However, if you think GDB should simply search farther back
from 0x6f34732e for code which looks like the beginning of a
function, you can increase the range of the search using the `set
heuristic-fence-post' command.
(gdb) q

Re: 新的qq插件 pidgin-lwqq 0.4.0 更新

发表于 ： 2015-02-12 20:46
由 newton1972
还有一种总线错误
No4

代码： 全选

(gdb) r
Starting program: /usr/bin/pidgin 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/mipsel-linux-gnu/libthread_db.so.1".
[New Thread 0x71167300 (LWP 4740)]
[New Thread 0x703ff300 (LWP 4743)]
[New Thread 0x6fbff300 (LWP 4744)]

Program received signal SIGBUS, Bus error.
0x5443356c in ?? ()
(gdb) bt full
#0  0x5443356c in ?? ()
No symbol table info available.
#1  0x5443356c in ?? ()
No symbol table info available.
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) q
盼大神指导

Re: 新的qq插件 pidgin-lwqq 0.4.0 更新

发表于 ： 2015-02-17 15:13
由 warmsun
archlinux里面的包似乎还是有问题 不知道是谁在维护 :em06

Re: 新的qq插件 pidgin-lwqq 0.4.0 更新

发表于 ： 2015-03-02 15:04
由 gdgglhy
更新后有两天可以用，现在又是一打开就关闭pidgin，QQ真的没救了

Re: 新的qq插件 pidgin-lwqq 0.4.0 更新

发表于 ： 2015-05-04 23:08
由 hlsq
现在登录时提示：“Network Error”。

Re: 新的qq插件 pidgin-lwqq 0.4.0 更新

发表于 ： 2015-06-10 20:06
由 frend
为什么执行sudo add-apt-repository ppa:lainme/pidgin-lwqq的时候会出现
Cannot add PPA: 'ppa:lainme/pidgin-lwqq'.
Please check that the PPA name or format is correct.
这是为什么 啊？我该怎么解决？求大神相助！
所有显示的时间为 UTC+08:00
分页： 80 / 81

由 phpBB® Forum Software © phpBB Limited 提供支持

简体中文语言由 phpBB Chinese 制作并提供支持