Please provide the informations about the process state,
gdb stack trace, and fragment of log generated using SIGUSR2 as
pointed out previously if you reproduce this with 0.0.19 .
If you have a reproducable way to trigger this, then switch
gam_server before the problem to debugging mode with SIGUSR2,
make it hang following your recipe, kill it and provide the output
debug found in /tmp as an attachment to this bug.
Please provide the informations about the process state,
gdb stack trace, and fragment of log generated using SIGUSR2 as
pointed out previously if you reproduce this with 0.0.19 .
http:// www.gnome. org/~veillard/ gamin/debug. html#Debugging1
If you have a reproducable way to trigger this, then switch
gam_server before the problem to debugging mode with SIGUSR2,
make it hang following your recipe, kill it and provide the output
debug found in /tmp as an attachment to this bug.
thanks,
Daniel