Something is more seriously wrong than the code.  The arguments in trace #7 look like there's some sort of memory corruption.  If you can reliably reproduce this, try running it in valgrind and see what errors it gives you.  Otherwise, let us know exactly what you have to do to reproduce it.  Because the constructor for QValueVector is given a constant of 4, it *shouldn't* ever be 139477320, so I'm inclined to claim that this is either a bad link/compile/compiler, an alpha particle hitting your ram, overheating, or something of that sort.

I'm closing this as a WORKSFORME.  Please reopen it if you can reproduce it after a fresh compile.  

Rebuild today, from a new svn check out and same problem...

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1240230208 (LWP 14316)]
[KCrash handler]
#6  0xb5bc2e3a in qFill<int*, int> (first=0x84dc280, last=0x84dc290, 
    val=@0xbfb312f4) at qtl.h:103
#7  0xb5bc3534 in QValueVector (this=0xbfb312ec, n=139313808, val=@0x0)
    at qvaluevector.h:492
#8  0xb5bc2212 in MSNChallengeHandler::computeHash (this=0x85132e8, 
    challengeString=@0xbfb31810) at msnchallengehandler.cpp:49
#9  0xb5babaad in MSNNotifySocket::parseCommand (this=0x82ffaa8, 
    cmd=@0xbfb318f0, id=0, data=@0xbfb318ec) at msnnotifysocket.cpp:549
#10 0xb5b93cab in MSNSocket::parseLine (this=0x82ffaa8, str=@0xbfb31950)
    at msnsocket.cpp:527
#11 0xb5b96f91 in MSNSocket::slotReadLine (this=0x82ffaa8)
    at msnsocket.cpp:457
#12 0xb5b98422 in MSNSocket::slotDataReceived (this=0x82ffaa8)
    at msnsocket.cpp:412
#13 0xb5b9a15b in MSNSocket::qt_invoke (this=0x82ffaa8, _id=9, _o=0xbfb31cfc)
    at msnsocket.moc:231
#14 0xb5ba83d7 in MSNNotifySocket::qt_invoke (this=0x82ffaa8, _id=9, 
    _o=0xbfb31cfc) at msnnotifysocket.moc:391
#15 0xb6945e29 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#16 0xb69468c4 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#17 0xb70b4f56 in KNetwork::KClientSocketBase::readyRead ()
   from /usr/lib/libkdecore.so.4
#18 0xb70b4f82 in KNetwork::KClientSocketBase::slotReadActivity ()
   from /usr/lib/libkdecore.so.4
#19 0xb70bc3c9 in KNetwork::KBufferedSocket::slotReadActivity ()
   from /usr/lib/libkdecore.so.4
#20 0xb70c301a in KNetwork::KBufferedSocket::qt_invoke ()
   from /usr/lib/libkdecore.so.4
#21 0xb6945e29 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#22 0xb6946738 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#23 0xb6cd9bef in QSocketNotifier::activated () from /usr/lib/libqt-mt.so.3
#24 0xb696616e in QSocketNotifier::event () from /usr/lib/libqt-mt.so.3
#25 0xb68dbdc6 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#26 0xb68dbfc2 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#27 0xb7060d7d in KApplication::notify () from /usr/lib/libkdecore.so.4
#28 0xb686d0ef in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#29 0xb68cd8e3 in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/libqt-mt.so.3
#30 0xb6880edb in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#31 0xb68f48b7 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#32 0xb68f47da in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#33 0xb68da8d5 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#34 0x08073702 in main (argc=139313808, argv=0x84dc290) at main.cpp:107

Result of valgrind:

http://cedric.bellegarde.free.fr/kopete_valgrind

#6  0xb5bc2e3a in qFill<int*, int> (first=0x84dc280, last=0x84dc290, 
     val=@0xbfb312f4) at qtl.h:103 
#7  0xb5bc3534 in QValueVector (this=0xbfb312ec, n=139313808, val= 0x0)
    at qvaluevector.h:492

These lines are troubling.  The constructor is called with n=4, which is hardcoded, so this n=139313808 doesn't really make sense.  Further, first-last is 4 words, so I know that the wacko value isn't actually being passed.  It looks like something's munging up the stack; either it's an -fomg-fast compile flag, a broken C compiler, or a stack overflow inside Qt (which I've verified isn't possible in my breezy 3.3.6).

I try building kopete with gcc 3.4, same bug ... :(

I just build kopete on my laptop (dapper drake too) and it works :-/

I install this build on my computer and it works !!!

I really don't understand what is happening :-(

Anyway, it works, i close this bug report.