crash on opening message

[laggard]

I have received a regular message that crashes licq every time I try to read it. When I open licq again the message is still there waiting for me to read it. When I click on the user that sent the message, my last sent message opens. Since the message is still waiting to be read, I close that last sent message and click the user's name again. Licq crashes again. I tried today's daily build and it did the same.

Strangely enough, I can look in the message history and see the message and it looks normal to me.

[emostar]

Logged In: YES user_id=21415

Can you provide us with some more details? os/gcc/qt/kde versions... and a backtrace would be great if you can enable debugging! This is strange, as I have not experience this ever.

[laggard]

Logged In: YES user_id=957862

I have never had this problem either. Unfortunately, I seriously doubt I can cause it to happen again. The backtrace I attached is what happens when I run licq through gdb. This seems to be caused by licq trying to read a message that isn't actually waiting to be read and not by the original problem unfortunately. I'm sorry I am so unhelpful.

config options $ ./configure --with-gnu-ld --enable-debug config options for qt plugin $ ./configure --with-gnu-ld --enable-debug --with-x --with-kde

uname -a: Linux matilda 2.6.1 #666 SMP Sat Jan 17 21:23:38 MST 2004 i686 unknown unknown GNU/Linux

gcc version 3.2.3

qt-3.2.1

KDE 3.1.4

[laggard]

Logged In: YES user_id=957862

By the way, changing the "NewMessages?" field in the user's file in the .licq/users directory from 1 to 0 solved the problem.

[emostar]

Logged In: YES user_id=21415

Has this happened since then? I still have never seen this.. so I'm not sure how to reproduce it or fix it since it is extremely rare.

[saspipi]

Logged In: YES user_id=1082085

I had the same problem a few mounth ago. Never seen it before. What I can add is the message that crashes licq has a totally black message field (with no characters?) and I was able to read other messages from the same user but at the point of reading this black msg licq crashed and a more important thing, that it's happend when I tried to transfer a file with wrong NAT config. The IP of the gateway has changed but the portforward rules had the old IP as the targetIP of the packet that should had forwarded to my PC. Produced this three of four times until the NAT has been properly set.

[nobody]

Logged In: NO

I had the same problem alot of times I had to manually delete the user history file and the msg would disappear.