Licq crashes

[nobody]

Licq 1.3.0 crashes very oft on send or receive messages. Today I see on log.errors:

10:28:08: [???] Unbekannter ICBM-Fehler: 0x000d

But I didn't see this message other time when Licq crashes.

I use Licq on a Fedora Core 2, with the KDE-Plugin. I compiled Licq from source.

Luca Bertoncello lucabert(at)lucabert(dot)de

[emostar]

Logged In: YES user_id=21415

We'll need some more information than this. Please run Licq in a xterm to show the debug output.. 'licq -d31' wil show as much information as possible.

Jon

[nobody]

Logged In: NO

I tryed to run licq with debug info... After some try, I get this:

21:24:48: [TCP] Message from anika (297677809). 21:24:48: [PKT] Unencrypted (ICQ) TCP Packet (40 bytes):

0000: 02 00 00 00 00 DA 07 0E 00 FB FF 00 00 00 00 00 .....Ú...ûÿ....

.

0010: 00 00 00 00 00 00 00 01 00 00 00 00 00 01 00 00 ................ 0020: 00 00 00 00 FF FF FF 00 ....ÿÿÿ.

21:24:48: [PKT] Packet (TCPv8, 40 bytes) sent:

(213.54.193.13:47596 -> 192.168.1.2:39591)

0000: 02 83 CC F1 D7 66 3D 68 98 31 C5 66 98 00 00 00 ..Ìñ×f=h.

1Ã…f....

0010: 00 00 00 00 00 00 00 01 00 00 00 00 00 01 00 00 ................ 0020: 00 00 00 00 FF FF FF 00 ....ÿÿÿ.

sox: Can't open input file '/usr/share/licq/sounds/icq/Message.wav': No such file or directory 21:24:48: [PKT] Packet (SRVv0, 6 bytes) sent:

(213.54.193.13:47598 -> 64.12.25.100:5190)

0000: 2A 05 3E 90 00 00 *.>...

Der Wecker klingelt

Sorry, my Licq is in german... I see, it trys to use a wav that does not exist. I correct the path, an I started Licq again. I have an unread message from the other part. If I doubleclick on the message and I get:

free(): invalid pointer 0x8a246c8! Der Wecker klingelt

If I want to use Licq again, I have to delete the file with the history of the user... This file, at the end, look like so:

[ R | 0001 | 2030 | 0001 | 1106511888 ] :Non riesco proprio a capire... :Sembra proprio che tutto funzioni alla perfezione...

Sorry, I wrote the tests in italian... Too many languages...

Anyway, if I delete this file, I can use Licq again.

I get the problem with Licq 1.2.7 and 1.3.0.

Hope to help to find the bug... Thanks Luca Bertoncello lucabert(at)lucabert(dot)de