freetalk-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Freetalk-dev] Freetalk 1.90 [jingle version] released


From: Matthias Quasthoff
Subject: Re: [Freetalk-dev] Freetalk 1.90 [jingle version] released
Date: Sat, 26 Aug 2006 07:19:19 +0200

Hi Vikas,

Am Freitag, den 25.08.2006, 15:57 +0530 schrieb Vikas Gorur:
> This is a "developers only" release, so there are bound to be a lot of
> bugs ;). Please report any that you find to this list.
I'm not sure whether I'm doing something wrong. Trying to build
freetalk--jingle with gcc 4.1.1 I receive lot's of errors and warnings.
For example, in order to be able to build at all I had to do

---  static const std::string XmppPump::strerror(buzz::XmppEngine::Error
err);
+++  static const std::string strerror(buzz::XmppEngine::Error err);

in src/xmpppump.h and similar stuff in three places in
libjingle/talk/base. After about 200 warnings I could run install and
run freetalk, but it doesn’t display anything. gdb says

> Starting program: /opt/freetalk--jingle/bin/freetalk 
> Reading symbols from shared object read from target memory...done.
> Loaded system supplied DSO at 0x53d000
> [Thread debugging using libthread_db enabled]
> [New Thread -1208822064 (LWP 21048)]
> 
> 
(waited about 20 seconds)
> Program received signal SIGTSTP, Stopped (user).
> [Switching to Thread -1208822064 (LWP 21048)]
> 0x0053d402 in __kernel_vsyscall () at ../../talk/base/socket.h:112
> 112       virtual ~Socket() {}
> (gdb) bt
> #0  0x0053d402 in __kernel_vsyscall () at ../../talk/base/socket.h:112
> #1  0x0096897e in __lll_mutex_lock_wait ()
> at ../../talk/base/socket.h:112
> #2  0x0096522f in _L_mutex_lock_71 () at ../../talk/base/socket.h:112
> #3  0x0096500e in pthread_mutex_lock ()
> at ../../talk/base/socket.h:112
> #4  0x080eccc8 in cricket::MessageQueueManager::Add (this=0x9c120e0,
> message_queue=0x9c12060) at ../../talk/base/criticalsection.h:93
> #5  0x080ee09f in MessageQueue (this=0x9c12060, ss=0x0) at
> messagequeue.cc:90
> #6  0x080efcdf in Thread (this=0x9c12060, ss=0x0) at thread.cc:99
> #7  0x080f05e4 in ThreadManager (this=0x8157380) at thread.cc:48
> #8  0x080f0676 in __static_initialization_and_destruction_0
> (__initialize_p=Variable "__initialize_p" is not available.
> ) at thread.cc:41
> #9  0x081168a5 in __do_global_ctors_aux ()
> #10 0x08058a8d in _init () at ../../talk/base/socket.h:112
> #11 0x0811684e in __libc_csu_init ()
> #12 0x005706c9 in __libc_start_main () at ../../talk/base/socket.h:112
> #13 0x0805a001 in _start () at ../../talk/base/socket.h:112

Have you experienced that?

Thanks,
Matthias





reply via email to

[Prev in Thread] Current Thread [Next in Thread]