Re: Bonobo Activation Server goes to sleep

Shmyrev wrote:

>Well, it seems that there is problem in esd, but it is hardly 
>reproducable. Could you get more info like: 
> 
>1. Build esd with options  
>$./configure --enable-debugging 
>and get esd log. 
>  
>

My esd is configured to enable debugging, and includes some customised 
debug output of my own. For that matter, I have also enabled debugging 
in gnome-session and the bonbo-activation-server. For gnome-session I 
defined and exported the GSM_VERBOSE_DEBUG environment variable, and all 
its debug output is indicated by the "gsm verbose" prefix in the log 
file. For the bonobo-activation-server, I compiled with the defined 
macro BONBO_ACTIVATION_DEBUG and exported the 
BONOBO_ACTIVATION_DEBUG_OUTPUT environment variable. From runlevel 3 I 
ran the command

startx >& logs/startx.log

This produced a 52K file, available from:

http://www.users.bigpond.com/geoffreyhacker/Logs/startx.log

>2. Use esd commands when server locks up and get output. 
>$esdctl serverinfo 
>$esdctl allinfo 
>$esdctl play somefile.wav
>

All three commands simply hung, and had to be moved to the background to 
regain the command prompt.

>3. Get backtrace from esd by attaching to it's process 
>$gdb --pid=... 
>  
>

Backtrace was:

#0  0xffffe002 in ?? ()
#1  0x0804a714 in main (argc=2, argv=0x0) at esd.c:976
#2  0x42015574 in __libc_start_main () from /lib/tls/libc.so.6

Cheers,

Geoff