Re: [Licq-main] Licq 1.3.1/SSL segfaulting (VERY LONG!!)
On Tuesday 19 April 2005 00:13, Rikard Johnels wrote: So right now i have decided its way to complicated to get a newer version than the one on released for SuSE via the homepage. Which SuSE version are you using? Bye, Thomas pgpqQ7Dl0kXN8.pgp Description: PGP signature
Re: [Licq-main] Licq 1.3.1/SSL segfaulting (VERY LONG!!)
On Friday 18 March 2005 23.47, Rikard Johnels wrote: On Tuesday 08 February 2005 09.55, Rikard Johnels wrote: On Tuesday 08 February 2005 09.37, wwp wrote: Hello Rikard, On Tue, 8 Feb 2005 09:18:19 +0100 Rikard Johnels [EMAIL PROTECTED] wrote: Hi all! Have a 1.3.1/SSL install (from SuSE apt) that keeps segfaulting. I usually keep it logged on and set the status to Not Available and Invisible If i leave it up, it segfaults after a period of time (differs from time to time) As far as i can see it is when i get a pending message from a offline user. Then it dies with segfault, and if i start it i get; [EMAIL PROTECTED]:~ licq 09:12:40: [WRN] Licq: Ignoring stale lockfile (pid 30338) Segmentation fault -- Lots of lines cut --- Still no ideas on what this can be? The problem is persistent and very easily reproduced. licq-1.3.1-20050224 -- /Rikard Sharing knowledge is the most fundamental act of friendship. Because it is a way you can give something without loosing something. -R. Stallman --- Rikard Johnels email : [EMAIL PROTECTED] Web : http://www.rikjoh.com/users/rikjoh Mob : +46 735 05 51 01 PGP : 0x461CEE56 --- --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ LICQ-Main mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-main
Re: [Licq-main] Licq 1.3.1/SSL segfaulting (VERY LONG!!)
On 4/19/05, Rikard Johnels [EMAIL PROTECTED] wrote: Still no ideas on what this can be? The problem is persistent and very easily reproduced. I have not been able to reproduce this locally. You said it happens when you get an offline message from a user? Is it a new user or one on your list? Also, can you try running the latest daily snapshot and using ./configure --enable-debug to provide as much details as possible? Jon --- This SF.Net email is sponsored by: New Crystal Reports XI. Version 11 adds new functionality designed to reduce time involved in creating, integrating, and deploying reporting solutions. Free runtime info, new features, or free trial, at: http://www.businessobjects.com/devxi/728 ___ LICQ-Main mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-main
Re: [Licq-main] Licq 1.3.1/SSL segfaulting (VERY LONG!!)
On Tuesday 19 April 2005 02.07, Rikard Johnels wrote: On Tuesday 19 April 2005 01.12, Jon Keating wrote: On 4/19/05, Rikard Johnels [EMAIL PROTECTED] wrote: Still no ideas on what this can be? The problem is persistent and very easily reproduced. I have not been able to reproduce this locally. You said it happens when you get an offline message from a user? Is it a new user or one on your list? Also, can you try running the latest daily snapshot and using ./configure --enable-debug to provide as much details as possible? Jon --- This SF.Net email is sponsored by: New Crystal Reports XI. Version 11 adds new functionality designed to reduce time involved in creating, integrating, and deploying reporting solutions. Free runtime info, new features, or free trial, at: http://www.businessobjects.com/devxi/728 ___ LICQ-Main mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-main Went back to 1.3.0 rpm for SuSE 9.2 as per the homepage. It works as expected. I dont have all the libraries and things to do a compile on my system, but ill try to check into that asap. I cant get it to compile the configurescript licq-20050419 make -f Makefile.cvs This Makefile is only for the CVS repository This will be deleted before making the distribution *** Concatenating configure tests into acinclude.m4 *** Retrieving configure tests needed by configure.in Can't locate object method path via package Request at /usr/share/autoconf/Autom4te/C4che.pm line 69, GEN1 line 112. aclocal: autom4te failed with exit status: 1 make[1]: *** [cvs] Error 1 make: *** [all] Error 2 So right now i have decided its way to complicated to get a newer version than the one on released for SuSE via the homepage. I'll stick with 1.3.0/ssl from the Mar 18 2005 -- /Rikard Sharing knowledge is the most fundamental act of friendship. Because it is a way you can give something without loosing something. -R. Stallman --- Rikard Johnels email : [EMAIL PROTECTED] Web : http://www.rikjoh.com/users/rikjoh Mob : +46 735 05 51 01 PGP : 0x461CEE56 --- --- This SF.Net email is sponsored by: New Crystal Reports XI. Version 11 adds new functionality designed to reduce time involved in creating, integrating, and deploying reporting solutions. Free runtime info, new features, or free trial, at: http://www.businessobjects.com/devxi/728 ___ LICQ-Main mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-main
Re: [Licq-main] Licq 1.3.1/SSL segfaulting (VERY LONG!!)
On Tuesday 08 February 2005 09.37, wwp wrote: Hello Rikard, On Tue, 8 Feb 2005 09:18:19 +0100 Rikard Johnels [EMAIL PROTECTED] wrote: Hi all! Have a 1.3.1/SSL install (from SuSE apt) that keeps segfaulting. I usually keep it logged on and set the status to Not Available and Invisible If i leave it up, it segfaults after a period of time (differs from time to time) As far as i can see it is when i get a pending message from a offline user. Then it dies with segfault, and if i start it i get; [EMAIL PROTECTED]:~ licq 09:12:40: [WRN] Licq: Ignoring stale lockfile (pid 30338) Segmentation fault I have no idea where to look or even what to look for. Any ideas? Providing a backtrace would help! This implies building w/ debug options (for instance: ./configure --enable-debug make make install; don't make install-strip!), and running licq from gdb. If possible use code from CVS. When licq segfaults, you are still under gdb, then type bt or bt full and send the full output to this mailing-list. Let us know if you need more help around building licq or running licq from gdb! Regards, Its a prebuilt package sparhawk:~ # file /usr/bin/licq /usr/bin/licq: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.2.5, dynamically linked (uses shared libs), not stripped (gdb) run Starting program: /usr/bin/licq [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 15380)] 09:46:58: [WRN] Licq: Ignoring stale lockfile (pid 25357) [New Thread 32769 (LWP 15382)] [New Thread 16386 (LWP 15383)] [New Thread 32771 (LWP 15384)] [New Thread 49156 (LWP 15385)] [New Thread 65541 (LWP 15386)] [New Thread 81926 (LWP 15389)] [New Thread 98311 (LWP 15390)] [Thread 98311 (LWP 15390) exited] [Thread 81926 (LWP 15389) exited] [New Thread 114696 (LWP 15391)] [Thread 114696 (LWP 15391) exited] [New Thread 131081 (LWP 15392)] [Thread 131081 (LWP 15392) exited] [New Thread 147466 (LWP 15393)] [New Thread 163851 (LWP 15394)] [Thread 163851 (LWP 15394) exited] [Thread 147466 (LWP 15393) exited] [New Thread 180236 (LWP 15395)] [Thread 180236 (LWP 15395) exited] [New Thread 196621 (LWP 15396)] [Thread 196621 (LWP 15396) exited] [New Thread 213006 (LWP 15397)] [Thread 213006 (LWP 15397) exited] [New Thread 229391 (LWP 15398)] [New Thread 245776 (LWP 15399)] [Thread 229391 (LWP 15398) exited] [Thread 245776 (LWP 15399) exited] [New Thread 262161 (LWP 15400)] [Thread 262161 (LWP 15400) exited] [New Thread 278546 (LWP 15401)] [Thread 278546 (LWP 15401) exited] [New Thread 294931 (LWP 15402)] [Thread 294931 (LWP 15402) exited] [New Thread 311316 (LWP 15403)] [Thread 311316 (LWP 15403) exited] [New Thread 327701 (LWP 15404)] [Thread 327701 (LWP 15404) exited] [New Thread 344086 (LWP 15406)] [Thread 344086 (LWP 15406) exited] [New Thread 360471 (LWP 15407)] [Thread 360471 (LWP 15407) exited] [New Thread 376856 (LWP 15408)] [Thread 376856 (LWP 15408) exited] [New Thread 393241 (LWP 15409)] [Thread 393241 (LWP 15409) exited] [New Thread 409626 (LWP 15410)] [Thread 409626 (LWP 15410) exited] [New Thread 426011 (LWP 15411)] [Thread 426011 (LWP 15411) exited] [New Thread 442396 (LWP 15412)] [Thread 442396 (LWP 15412) exited] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 65541 (LWP 15386)] 0x40c8e96a in QListViewItem::listView () from /usr/lib/qt3/lib/libqt-mt.so.3 (gdb) bt full '#0 0x40c8e96a in QListViewItem::listView () from /usr/lib/qt3/lib/libqt-mt.so.3 No symbol table info available. #1 0x404fb2c9 in CUserViewItem::~CUserViewItem () from /usr/lib/licq/licq_kde-gui.so No symbol table info available. #2 0x404fb439 in CUserViewItem::~CUserViewItem () from /usr/lib/licq/licq_kde-gui.so No symbol table info available. #3 0x404fb439 in CUserViewItem::~CUserViewItem () from /usr/lib/licq/licq_kde-gui.so No symbol table info available. #4 0x404fb439 in CUserViewItem::~CUserViewItem () from /usr/lib/licq/licq_kde-gui.so No symbol table info available. #5 0x404fb439 in CUserViewItem::~CUserViewItem () from /usr/lib/licq/licq_kde-gui.so No symbol table info available. #6 0x404fb439 in CUserViewItem::~CUserViewItem () from /usr/lib/licq/licq_kde-gui.so No symbol table info available. #7 0x404fb439 in CUserViewItem::~CUserViewItem () from /usr/lib/licq/licq_kde-gui.so No symbol table info available. #8 0x404fb439 in CUserViewItem::~CUserViewItem () from /usr/lib/licq/licq_kde-gui.so No symbol table info available. #9 0x404fb439 in CUserViewItem::~CUserViewItem () from /usr/lib/licq/licq_kde-gui.so No symbol table info available. #10 0x404fb439 in CUserViewItem::~CUserViewItem () from /usr/lib/licq/licq_kde-gui.so No symbol table info available. #11 0x404fb439 in CUserViewItem::~CUserViewItem () from /usr/lib/licq/licq_kde-gui.so No symbol table info available. #12 0x404fb439 in CUserViewItem::~CUserViewItem () from /usr/lib/licq/licq_kde-gui.so No symbol table info available. #13 0x404fb439 in
